<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
0D50Z00008G7UcfSAFOkta Classic EngineLifecycle ManagementAnswered2024-04-17T09:43:41.000Z2015-11-06T16:18:39.000Z2017-08-17T18:18:22.000Z
3tvcl likes this.
  • 3tvcl (3tvcl)

    This would be truely awesome. We would use it to help deploy Amazon Workspaces. Have you tried it yet?
  • Chris Dodds (Customer)

    I can confirm the connector worked for me when I tested yesterday. I haven't tried anything advanced yet (multiple UPNs, etc), just spun up an instance, installed the agent, and pushed some test users.

     

    I'm still trying to decide if this path is going to work, but it's mostly around Samba4 limitations. I'm also not sure if it would be possible to automate the AD agent install & web auth as part of a server bootstrap.
    Expand Post
  • 3tvcl (3tvcl)

    I did some setup with this tonight, I think it may work in our use cases if I can figured out how to have okta users created in Simple AD. If it were a different okta app I could consider this provisioning. Sending in a support ticket. Let me know if you make any progress on your side.
  • Chris Dodds (Customer)

    You just need to spin up an instance that's joined to SimpleAD and install the Okta AD agent on it. Use directory provisioning instead of app provisioning. Works fine.
  • 3tvcl (3tvcl)

    UI wise is that showing up for you in the Directires area. 0EMF0000000DXkH
  • 3tvcl (3tvcl)

    Chirs, I must be missing something. 

     

    How do I tell Okta to create the user (from okta info) in the directory via the AD Agent?
  • Chris Dodds (Customer)

    Create an Okta group, assign the group to the directory, assign users to the group. If you want the actual security group to appear in the directory as well you configure Push Groups in the directory settings.
This question is closed.
Loading
Using Okta AD Connector with AWS Simple AD