Authentication

Start with the unified Login node. Its guided method picker comes from registered identity authorities and credential sources. UCIK acquires non-variable SDK credentials such as Steam tickets and Discord OAuth tokens; your graph supplies only values a player or game chooses, such as a display name, exchange code, developer credential, username, password, or challenge response.

• Fixed login screen: select the method on the node and wire the generated fields.
• Runtime login screen: switch the node to runtime request mode, call Get Login Methods, render each descriptor, and submit FUCIK_LoginRequest.
• Automatic login: use the Auto method; it follows the ordered routes in UCIK settings.

Success returns a stable primary Player handle and an Identity map. Query secondary handles with Get Identity Handle instead of relying on provider-specific output pins. Interactive and challenge-based routes continue through Continue Login; Cancel Login releases the operation.

Use Logout with its Blueprint bitmask scope. With the default scope, UCIK logs out the authority that created the identity. See Choosing a login method for complete recipes.

Use the per-kit login nodes only when you need that SDK's platform-exact option set rather than a portable identity.