What is an Alien Provider? Register Your App on Alien Network

An Alien Provider is the on-chain representation of your application, mini app or web app on the Alien Network. It serves as your application’s verified identity within the system.

How Alien Providers Work

Before users can verify and authenticate with your application using Alien SSO, you must create a Provider: a blockchain-based entity that represents your application. A Provider has multiple roles:

• Your app’s identity on the Alien Network.
• A trust anchor for users to verify they’re connecting with your legitimate app.
• An access control mechanism that defines where and how authentication can occur.

Stored on Alien Network

Provider ownership is anchored on Alien Network as a permanent, verifiable record. Mutable metadata — allowed origins, provider URL, name and logo — is served from the off-chain Developer Portal and checked alongside the on-chain record on every request. This ensures:

• Immutability: the on-chain provider record cannot be tampered with or altered without authorization.
• Transparency: anyone can verify a provider’s authenticity and configuration.
• Decentralization: no central registry controls provider ownership.
• Privacy: user data remains under user control and is never exposed on-chain.
• Trust: users can cryptographically verify they’re connecting with legitimate applications.

Managed with Alien ID

Providers are created and managed by developers through their Alien ID:

• Provider creation requires authorization via Alien ID in the Developer Portal.
• Only the provider’s creator — identified by their Alien ID — can modify provider settings.
• All provider updates are signed with the creator’s private key.
• Provider ownership is tied to the creator’s Alien ID on-chain.

This ensures that only you, as the verified owner, can manage your application’s provider configuration.

Register Your Application as a Provider

All providers are created through the Developer Portal :

1. Access the Developer Portal

   • Open the Developer Portal .
   • Sign in with your Alien ID.

2. Create New Provider

   • Click “Create Provider”.
   • Scan the QR code with the Alien App.
   • Approve provider creation in the Alien App.

3. Configure Provider Settings

   • Name: display name shown to users during authentication.
   • Provider URL: the main URL of your application.
   • Allowed Origins: the origins where authentication is permitted.

   Origins match exactly. List every full origin (scheme + host + port) your app serves from — matching is exact string equality, with no domain or wildcard matching. Requests from unlisted origins are rejected. localhost and 127.0.0.1 are always allowed on any port for development.

4. Save and Deploy

   • The provider is registered on-chain.
   • You receive your Provider Address.
   • Use this address in your SDK configuration.

Provider Lifecycle

1. Creation

   • You set the provider’s name, URL and allowed origins.
   • Upload a logo and description.
   • Optionally configure claim requirements.

2. Integration

   • Use your provider address in SDK initialization.
   • Implement an authentication flow.
   • Test the integration with development origins.

3. Production

   • Authentication requests are verified against the provider’s metadata.
   • Users authenticate through your verified provider.
   • Sessions are created under your provider’s namespace.

4. Updates

   • Update allowed origins as needed.
   • Modify your provider metadata as needed.
   • Metadata changes take effect via the Developer Portal; ownership remains anchored on-chain.

Provider vs Session

It’s important to understand this distinction:

A useful analogy: a provider is your app’s passport, while sessions are entry visas for each user.

Next Steps

• What is an Alien Session? — learn about user sessions
• SSO Guide — integrate standard SSO
• Solana SSO Guide — link wallets on-chain
• Developer Portal  — create your provider