<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
0D50Z00008C3jRmSAJOkta Classic EngineAdministrationAnswered2018-10-31T23:13:18.000Z2018-01-10T00:49:10.000Z2018-10-31T23:13:18.000Z
Best practices for test and live environments
I am trying out the API products to use Okta for my application's authentication needs. My application will be deplyed in a staging environment and a live environment. How can I setup Okta to use it from both? If I use the same okta tenant (account), then my staging users get mixed up with the live users.

 

I did try setting both apps up as separate applications and then add users to groups assigned to the appropriate applications, but the fact remains that a user a@b.com (single okta user) will be used for staging and live. I would like to completely separate out those two. Any opinions / best-practices welcome.

RonnieB.86506 likes this.
  • mike.davie1.5312945692819849E12 (Customer First Programs)

    Hello Ashish!

     

    The best way to do this is to install and configure it on both environments and make sure that the connections are not mixed up. 

     

    Hope this helps!

     

    Mike Davie

    Okta Help Center

    Expand Post
  • RonnieB.86506 (Customer)

    Following this up ..Just to confirm the best alternative.

    This means is ok to have 2 separate okta organizations/accounts one for dev/staging and other for production? Is this the best practice?

    Is there any known consequence in doing this as opposed to keep everything in just 1 single organization?

     

    Thank you.

    Expand Post
This question is closed.
Loading
Best practices for test and live environments