Authorization for API access and Web SSO have traditionally been separate worlds. Currently they are typically deployed using SAML tokens, but sharing little common infrastructure. OpenID Connect as a profile of OAuth 2 starts to remove the need to deal with these as separate software stacks. The session will provide an overview of the following: The different participant rolls in Connect How JSON Web Tokens (JWT) are used How Connect provides both Authentication and Authorization tokens in a single flow How Connect can support Single Signon for Native Applications