Package com.codename1.backend.security.saml2
package com.codename1.backend.security.saml2
SAML 2.0 Web Browser SSO for this server as a service provider, shaped like
Spring Security's SAML module:
RelyingPartyRegistration describes an
identity provider, RelyingPartyRegistrations reads one from metadata or
the configuration, and http.saml2Login(...) wires the sign-in. The
response is judged by Saml2ResponseValidator. XML signatures are checked
by this package's own strict reader and exclusive canonicalization, which
accept only the shapes SAML signing produces. Not supported: encrypted
assertions and Single Logout.-
ClassDescriptionA fixed set of
RelyingPartyRegistrations.One identity provider this server accepts SAML 2.0 sign-ins from, and how this server presents itself to it.Builds aRelyingPartyRegistration.The identity providers SAML sign-ins are accepted from.MakesRelyingPartyRegistrations from an identity provider's metadata and from the configuration.The user an identity provider vouched for in a SAML assertion: the assertion's NameID, the attributes it stated, and the session indexes it gave.A user signed in through a SAML identity provider.Turns the user an identity provider vouched for into the authentication the application signs in: its authorities, and anything it looks up about the user in its own records.A SAML sign-in that was refused.An AuthnRequest on its way to the identity provider: the request itself, encoded for its binding, and how the browser is sent there.The reasons a SAML sign-in is refused, as the codes Spring Security uses.SAML Single Logout, front channel: theLogoutRequestandLogoutResponsethis server sends, and the checks on the ones it receives.A logout message this server received, after every check passed.A SAML protocol message on its way to the identity provider -- an AuthnRequest, a LogoutRequest or a LogoutResponse -- encoded for its binding, and how the browser is sent there.This server's SAML metadata, for the identity provider's administrator to load: who it is, where responses go, the key its requests are signed with, the keys assertions may be encrypted to, and where logout messages go.Decides whether a SAML 2.0Responsean identity provider posted signs a user in, following the Web Browser SSO profile (SAML 2.0 profiles, section 4.1.4) and Spring Security's defaults.