
c2ziv (c2ziv) asked a question.
hi,
Is it possible to implement concurrency rules via OKTA?
If I don’t want more than 100 people to access an application at a single time and we use OKTA for the authentication, can we block user 101 from logging in until there’s space free?

Short version is no. Longer version is also no, but with an explanation of why Okta can't do this. Okta has no sight of the state of your logged in users. It registers that a user has logged in at a point in time, but then redirects the authenticated user to your application. That user can then remain logged in, can logout locally, kill the cookie in their browser, close their browser, shutdown their laptop. Any event that will impact their logged in state happens on the client and Okta has no visibility of that. So it doesn't know if there are 100 logged in or 1000. Or 1. It does have a record of login events to your app, but not whether they are still logged in.
Your app is the only place where the current state is known via sessions.
You could ghetto it up and interogate the Okta logs for the authentication event metrics for your app and then make decisions based on that, but that's not the answer you want. It's also more effort than just have a record of valid sessions in your app and controlling access there.