<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A4oO0JCQUOkta Identity EngineAdvanced Server AccessAnswered2026-02-17T09:00:23.000Z2024-05-06T19:26:14.000Z2024-05-07T21:11:28.000Z

SebastienB.90492 (Customer) asked a question.

SMB Authentication Using Okta Advanced Server Access with Samba and PAM

Hello Okta Community,

 

I am managing a Linux cluster built with Alma Linux, currently configured to use Okta Advanced Server Access (OASA) for SSH authentication. As part of a new requirement, I need to set up SMB shares accessible to a Windows station. Our cluster is running in an isolated network without access to Active Directory.

 

I found in Okta documentation that I need to create an `sft.yaml` file but am unsure of the options I should include. According to a post I read, ScaleFT should intercept a PAM request and forward it to Okta for authentication.

 

Here are the configurations I'm planning to implement:

 

**`/etc/samba/smb.conf`:**

```ini

[global]

   security = user

   map to guest = bad user

   obey pam restrictions = yes

```

 

**`sft.yaml`:**

```yaml

PAM:

  Enabled: true

  ServiceName: "smb"

AccessControl:

  RequireSession: false

Labels:

  environment: "production"

  purpose: "smb-auth"

```

 

**Questions:**

Are these configurations correct for enabling SMB authentication through OASA?

Has anyone successfully set up a similar configuration, and what challenges did you encounter?

Are there any other recommendations or best practices for securing and optimizing this setup?

 

Any insights from those who have navigated similar integrations would be invaluable.

Thank you in advance for your support!


This question is closed.
Loading
SMB Authentication Using Okta Advanced Server Access with Samba and PAM