Introduction

Brazen's API and SSO support enable you to control how your users register to attend events. You don't have to use the API if you want to require your users to SSO with your company or app. You don't have to use SSO if you want to call the Brazen API. But, when combined together, you can create a variety of user experiences that make it easier for your users to register and attend events, or control who has access to your events.

Here are some the registration user experiences you can build with API and SSO:

1. user logs into your application and registers for the event using a registration form hosted in your application
2. user logs into your application and registers for the event using a registration form hosted on Brazen
3. user logs into Brazen and registers for the event using a registration form hosted in your application

If you are interested in users logging into your application, then take a look at Options 1-4. These flows illustrate how users can log into your application (either by starting in your application or from Brazen's login screen). Option 5 illustrates how you can host the registration form if you are not planning to use SSO with Brazen.

Before we begin, it is important to know that there are a number of standards that address authentication and authorization for web applications. These standards use different terms that refer to the same or similar concept, actor or interaction. This article uses "identity provider" or "IdP" to refer to Brazen customers who are using single sign-on (SSO), either SAML 2.0 or OpenID Connect, with Brazen. In all of these flows, Brazen acts as the "service provider" (SP), also called the "Relying Party" in OpenID

Option 1: IdP initiated SSO with SAML 2.0 + API event registration

Option 2: IdP initiated SSO with OpenID Connect + API event registration

Option 3: SP initiated SSO with SAML 2.0 + API event registration

Option 4: SP initiated SSO with OpenID Connect + API event registration

Option 5: API event Registration w/o SSO