GenAuth DocsDocuments
Concepts
User Guide
Development Integration
AgentAuth
Metadata
Development Integration
Multi-tenant (beta)
Console Documentation
Multi-tenant Console
Tenant Console
Saas Application Demo
Concepts
User Guide
Development Integration
AgentAuth
Metadata
Development Integration
Multi-tenant (beta)
Console Documentation
Multi-tenant Console
Tenant Console
Saas Application Demo
Old version

¶ APN Overview

Update time: 2025-07-23 07:34:21
Edit

APN (GenAuth Partner Network) is an application partnership network provided by GenAuth. After joining APN:

  • Your application will have single sign-on capability, allowing your customers to log in to your application through a unified entry point with a unified account
  • Makes it easier for your customers to find your application.

Before joining APN, your application needs to have OIDC capability. This guide includes four main sections:

  • Integrate OIDC into Your Application
  • Test OIDC Capability Based on GenAuth
  • Important Notes Before Joining APN
  • Submit Application

¶ Guide Reading Instructions

  • If your application does not yet have OIDC capability, please start reading from "Integrate OIDC into Your Application";

  • If your application already has OIDC capability, you can directly proceed to "Important Notes Before Joining APN" and "Submit Your Application to APN".

¶ About OIDC

  1. First, let's understand some terminology to help you better comprehend the following content.

IDP: Identity Provider

SP: Service Provider

Simply put, for example, if you developed a social App that uses WeChat interface for third-party login. In this process, WeChat is the IDP providing identity for users; your application is the SP providing services to users.

  1. Then let's understand what OpenID Connect is?

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It allows clients to verify the identity of end-users based on authentication performed by an authorization server, and obtain basic profile information about the end-user in an interoperable and REST-like manner.

OpenID Connect allows all types of clients (including web-based, mobile, and JavaScript clients) to request and receive information about authenticated sessions and end-users. The specification suite is extensible, allowing participants to use optional features when it makes sense for them, such as encryption of identity data, discovery of OpenID providers, and session management.

  1. What problems does OpenID Connect solve?

OpenID Connect 1.0 allows applications and site developers to authenticate users without taking on the responsibility of storing and managing passwords, as the internet is full of people trying to compromise user accounts for their own benefit.

  1. Why should developers use OpenID Connect?

Because it's simple, reliable, secure, and frees them from the difficult and dangerous task of storing and managing others' passwords. An additional benefit is that it also makes users' lives easier during signup and registration processes, thereby reducing site abandonment.

  1. Relationship between OIDC and SSO

SSO includes both unified login and unified logout. SSO implemented based on OIDC mainly utilizes OIDC service as a unified entry point for user authentication center, making all places requiring login handled by the OIDC service. More straightforwardly, it separates the user authentication part and hands it over to the OIDC authentication center.

  • Guide Reading Instructions
  • About OIDC

User identity management

Integrated third-party login
Customized authentication process

Enterprise internal management

Single sign-on
Multi-factor authentication
Permission management

Developer

Development Documentation
GitHub (opens new window)

Company

official@genauth.ai
16th Floor, Building B, Beichen Century Center, Chaoyang District, Beijing (Total)
Room 406, 4th Floor, Block B, No. 200, Tianfu Fifth Street, High-tech Zone, Chengdu (Branch)

© Beijing Steamory Technology Co., Ltd.