We have a development environment/sandbox for our title. We use an OpenID identity provider connected to our backend. Currently, it seems we are required to whitelist player account IDs (player-group) for every person needing access to our sandbox. This is inconvenient for us, as we are a large organization with frequent personnel changes.
Ideally, we would like our game to run in the Dev sandbox by default, without the need to manually add or remove users from our playgroup since it is laborious work. Also, it limits upto 500 entries, which may in the future be to little.
Is there a recommended way to give all our employees automatic access to play on one of our sandbox deployments? If not, are there any APIs available that would allow us to automate the whitelisting of account IDs? And what about this 500-member limit, do we create multiple groups when we reach a limit?
It would be really nice if, instead of typing an account ID (which I suppose is fetched from sub claim based on this doc) , we could specify a claim that is used for the whitelisting. Then we can whitelist on a tenancy ID, which separates our users internally. This is similar to the display name configuration in the identity provider, which allows us to configure the display name based on claims.
Hello, at the moment, we don’t have an alternative to managing player groups other than the Developer Portal, which supports manual and bulk input. However, we do have a feature request in our backlog to support wild card characters. If we were to add that feature, would this unblock you here? I think so based on your post, but I just want to make sure. I can bring this up with our engineering team, but I can’t promise anything at the moment.
It depends a bit on what you mean by a wildcard. A wild card there would not help a lot if you mean something like ‘player-*’ where * can be anything. Rather it would be nice to have what i asked above, is to allow changing which claim is used for matching the account id. Then we can for example, allow users that play in a certain environment
It looks like the current implementation (correct me if im wrong) reads the account id from the sub claim. The sub claim for us is our own user ID, which are big integer, so we have to add every new employee, which is quite a lot of overhead and easy to miss if no automation is possible.
You’re correct; the accountId is used, and yeah, supporting wildcards here wouldn’t help at all. I’ll create two feature requests: one to see if we can allow the user to configure which claim is used to allow access to the private deployment(s) and another to allow management via Web API.
For the 500 member limit, when you get close to it, please reach out via private discussion. Thanks!
[Content removed] Bergeron Are there any updates on allowing us to specify a claim to allow access to private deployments?
In my studio, we do things slightly different where our custom backend is run on each developer’s machine which means the AccountIds during development are throwaway and not stable. Having to add them to PlayerGroups means a deal-breaker amount of overhead in order to use the OpenID integration during development which is something we value highly (as it makes our workflows significantly more efficient for various reasons).
The proposed solution of allowing us to specify a “claim match” in case of OpenId providers would solve this for us as we could then add a claim to every token issued from each dev’s locally running backend and that’d be that.
Are there any updates you can offer on this?
There is no movement on this feature request at the moment. I created a KB article to help make it more visible that using claims is not currently supported. We’ll also use this article to provide updates when there are movements on this feature request.
https://dev.epicgames.com/community/learning/knowledge-base/bLkLa/epic-online-services-is-it-possible-to-use-claims-for-player-group-configuration-when-using-the-openid-identity-provider