Access control
Configure visibility and access permissions to control who can discover and join your sessions.
読み終わるまでの所要時間 1 分最終更新 1日前
By default, the MPS SDK accepts API calls from either an Authenticated Player or a Service Account. In some cases, you might want more control over how sessions are created or joined. In those cases you can use Access Control.
Service Account controlled sessions
In the following example, sessions can only be created and players can only join via a Service Account. Service accounts allow you to control the session by restricting write access for Players. Creating project policies via CLI with the following JSON definition willDenyUpsert the policies with{ "statements": [ { "Sid": "DenyPlayerSessionWrites", "Resource": "urn:ugs:lobby:/v1/*", "Principal": "Player", "Action": ["Write"], "Effect": "Deny" }, { "Sid": "AllowPlayerSessionReconnect", "Resource": "urn:ugs:lobby:/v1/*/reconnect", "Principal": "Player", "Action": ["*"], "Effect": "Allow" }, { "Sid": "AllowPlayerSessionTokens", "Resource": "urn:ugs:lobby:/v1/*/tokens", "Principal": "Player", "Action": ["*"], "Effect": "Allow" } ]}
ugs access upsert-project-policy -p <project-id> -e <env-name> <file-path>403 - Forbidden