<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
0D51Y00006nTwdNSASOkta Classic EngineSingle Sign-OnAnswered2024-03-25T19:04:13.000Z2019-10-21T14:35:49.000Z2019-10-23T22:53:18.000Z

h6gdi (h6gdi) asked a question.

Advanced Server Access: Server enrollment in wrong project

We are currently using the Advanced server access product and have three different projects within our Team(qa, staging and production), our servers are hosted on amazon AWS, we do not have account wide server enrollment on any project, we enroll servers via per project enrollment tokens which get provisioned on startup.

 

The issue we are facing is that we are seeing servers from the qa and staging project being enrolled in the production project, we have checked every machine and they have the tokens that correspond to their respective qa and staging projects yet they get enrolled onto the production project.


  • Hi Sabastian,

     

    I suggest creating a case with Okta Support, since this issue will require some troubleshooting and examination of your configuration.

     

    Thanks,

     

    Brian Anderson

    KCS Specialist

    Okta

    Expand Post
    Selected as Best
  • Hi Sabastian,

     

    I suggest creating a case with Okta Support, since this issue will require some troubleshooting and examination of your configuration.

     

    Thanks,

     

    Brian Anderson

    KCS Specialist

    Okta

    Expand Post
    Selected as Best
This question is closed.
Loading
Advanced Server Access: Server enrollment in wrong project