GS2-Identifier API Reference

This function manages credentials and privileges for accessing GS2.

When accessing GS2, credentials are used to call the API. The processing is based on the security policy assigned to the user who owns the credential. If multiple security policies are assigned to a user, the API can be used as long as one of the security policies allows the operation.

Multiple people can manage a single project by creating management console login passwords.

GS2-Identifier provides concepts equivalent to IAM (Identity and Access Management) in cloud services.

A security policy is a permission definition written in JSON format. By describing the resource GRNs to allow and the actions to allow (operation identifiers such as Gs2Account:CreateAccount), it expresses what operations are permitted for users to whom the policy is attached.

The client ID and client secret issued to a user are used as authentication information when calling GS2 APIs. Multiple credentials can be issued per user, and you can use them appropriately for different purposes or devices.

As an exception, login for a user (issuing a Project Token) may be performed on the application side. By calling the Login API with an embedded client ID / client secret and using the obtained Project Token as the authentication information for GS2 APIs, you can call APIs within the scope of the security policies associated with that user. Call the Login API using one of the general-purpose SDKs for each language (C# / Go / Python / TypeScript / PHP / Java) rather than through the Domain of the game-engine SDKs.

Combining this with GS2-Version allows permissions to be granted in stages. Give the credential embedded in the application only weak permissions, enough to perform login and a version check, and issue a Project Token after the version check passes so that the game itself is accessed with the stronger permissions.