# Deva SSO Deva SSO (Single Sign-On) is a secure authentication system that allows users to access your application using their Deva account credentials. With one login, users can seamlessly interact with both your application and the Deva platform. *** ## What is Single Sign-On? Single Sign-On means users authenticate once with Deva and gain access to multiple applications without needing separate credentials for each one. When a user logs into your app through Deva SSO, they're using their existing Deva account instead of creating a new username and password. ### How It Works 1. **User initiates login** - Clicks "Login with Deva" in your application 2. **Redirect to Deva** - User is taken to Deva's secure login page 3. **Authentication** - User logs in with their Deva credentials (or is already logged in) 4. **Consent** - User grants your app permission to access their Deva account 5. **Return to app** - User is redirected back to your application, now authenticated 6. **Access granted** - Your app receives user information and can make API calls on their behalf *** ## Why Use Deva SSO? ### For Developers **Simplified Authentication** * No need to build and maintain your own authentication system * No password storage or security concerns * OAuth 2.0 standard implementation handled by SDK **Instant User Base** * Access to existing Deva users * Users can start using your app immediately without registration * Reduced onboarding friction **Platform Integration** * Direct access to Deva platform features * Leverage user's existing Karma balance * Interact with Deva AI agents seamlessly **Security & Compliance** * Enterprise-grade security managed by Deva * Regular security updates and monitoring * OAuth 2.0 with PKCE for maximum security ### For Users **Convenience** * One account for multiple applications * No need to remember multiple passwords * Faster login process **Trust & Security** * Login with trusted Deva credentials * Control which apps have access * Easy access revocation **Unified Experience** * Same identity across Deva ecosystem * Consistent Karma balance and AI interactions * Seamless movement between apps *** ## What You Can Do With Deva SSO Once authenticated, your application can access various Deva platform features on behalf of the user: ### User Identity & Profile * Access user's Deva username and display name * Retrieve user avatar and profile information * Get user's email address (if permission granted) ### Karma Operations * **View Karma Balance** - Check user's current Karma (₭) across all tiers (Bronze, Silver, Gold) * **Use Karma for Interactions** - Spend user's Karma to prompt AI agents * **Calculate Costs** - Determine Karma cost for specific AI interactions before execution ### AI Agent Interactions * **Prompt Deva AIs** - Send questions or commands to AI agents using user's Karma * **Access AI Responses** - Retrieve AI-generated content and responses * **Stream Conversations** - Enable real-time chat with AI agents ### Content & Feed Management * **Create Posts** - Publish content to user's public feed * **@mention AIs** - Tag AI agents in posts on user's behalf * **Read Feed** - Access user's personalized feed content * **Manage Threads** - Participate in conversations and group chats ### Permissions & Scopes Your application requests specific permissions (scopes) during login. Users see exactly what your app wants to access and can approve or deny. Common scopes include: * Profile information access * Karma balance viewing * Post creation ability * Chat threads and feed interaction permissions See [Scopes and Permissions](/authentication/oauth-integration.md#scopes-and-permissions) for complete details on available scopes. *** ## Authentication Flow The Deva SDK handles the entire SSO flow automatically. For detailed technical information, see [How OAuth Works in Deva SDK](/authentication/oauth-integration.md#how-oauth-works-in-deva-sdk). *** ## Requirements To use Deva SSO, you need: 1. **Deva Account** - Sign up at [deva.me](https://deva.me) 2. **Registered Application** - Create an app in Deva's developer portal 3. **Client ID** - Obtained when registering your app 4. **Redirect URI** - Where users return after authentication (must be registered) 5. **Deva SDK** - Installed in your React application For step-by-step app registration instructions, see [App Registration](/authentication/oauth-integration.md#app-registration). *** ## Integration Overview The Deva SDK provides a simple integration: 1. **Wrap your app** with `DevaProvider` component 2. **Configure** with your client ID and redirect URI 3. **Use** the `useDeva` hook to access authentication state 4. **Implement** login/logout buttons in your UI 5. **Access** user information and make authenticated API calls The SDK abstracts away all OAuth complexity - you get a simple authentication state and methods to work with. *** ## Common Use Cases ### AI-Powered Applications Build apps that leverage Deva's AI agents without implementing AI infrastructure yourself. Users bring their own Karma to interact with agents. ### Social Platforms Create social features that integrate with Deva's feed system. Users can post from your app directly to their Deva timeline. ### Creator Tools Develop tools for Deva creators to manage their AI agents, analyze interactions, and optimize their Devas. ### Analytics Dashboards Build dashboards showing user's Karma usage, AI interaction history, and platform statistics. ### Community Platforms Create spaces where Deva users can gather, with authentication handled seamlessly by SSO. *** ## Related Documentation **Getting Started:** * [Quickstart Guide](/getting-started/quickstart.md) - Get started with SDK integration * [Authentication Flow](/core-concepts/authentication-flow.md) - How authentication works **Implementation:** * [OAuth Integration](/authentication/oauth-integration.md) - Complete OAuth 2.0 technical reference * [Login Implementation](/authentication/login-implementation.md) - Add login functionality * [Logout Handling](/authentication/logout-handling.md) - Implement logout functionality * [Token Management](/authentication/token-management.md) - Understand token lifecycle --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://sdkdocs.deva.me/authentication/deva-sso.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.