X

Set up X as a social login provider in SecureAuth Connect so users can sign in with their X account.

Register X as a provider

1. In your workspace, go to Authentication > Providers.

2. Click Create Connection.

3. Filter by Social Providers and select X.

4. Choose a registration mode:

   Mode	Description
   Embedded	Uses a client application registered by SecureAuth. No developer portal registration required.
   Bring your Own	Uses a client application registered by your organization. Requires registering an application in the X Developer Platform to obtain API Key and API Secret credentials.

   

5. Click Save.

Configuration

Setting	Description
Name	Display name for this provider. Default: X.
Display order	Controls the position of this provider on the sign-in page. Default: 0.

Use Try Sign-in to test the X sign-in flow. Use Delete Identity to remove this provider.

Attributes

X returns the following attributes after authentication:

Connector name	Friendly name	Data type	Scope
id	User ID	String	User Info
name	Name	String	User Info
username	Username	String	User Info
confirmed_email	Confirmed Email	String	User Info
first_name	First name	String	User Info
last_name	Last name	String	User Info

X uses username (the user's X handle) and confirmed_email rather than a standard email attribute. The confirmed_email attribute contains the email address verified by X.

To add custom attributes, click + Add attribute.

Mappings

Default attribute mappings from X to the SecureAuth authentication context:

Source	X source name	SecureAuth target name
User Info	Name	Name
User Info	First name	Given name
User Info	Last name	Family name
User Info	Confirmed Email	Email

To customize, click + Add mapping or + Add static mapping.

Provisioning

Provisioning controls what happens when a user authenticates through X.

Disabled

Users are not persisted in the user store. Authentication succeeds but no user record is created.

Just-in-Time Provisioning

Users are persisted in the user store on first login.

Identifier Correlation
Maps the incoming X identity to an existing user. Default: X Email ↔ Users Email.

Attribute Provisioning
Maps X attributes to user profile fields. Defaults:

• Email → Email
• Given name → First name
• Family name → Last name

Pre provisioning mode

Users must already exist in the user store before they can authenticate. New users are not auto-created at login; they must be added via an offline process.

Authentication flow control
Select what happens when no matching user is found:

• Deny – Terminate the authentication flow.
• Allow – Proceed with the authentication flow.

Identifier Correlation
Maps the incoming X identity to an existing user. Default: X Email ↔ Users Email.

Attribute Provisioning
Maps X attributes to user profile fields. Defaults:

• Email → Email
• Given name → First name
• Family name → Last name

Extensions

Extension	Description
Post Authentication script	A server-side script that runs after X authentication completes. Click Manage Script to configure.
Post Authentication application	A custom application that receives a callback after X authentication completes. Click Manage Custom App to configure.

See also

• Social login