{"type":"doc","content":[{"type":"heading","attrs":{"level":1},"content":[{"text":"Introduction","type":"text"}]},{"type":"paragraph","content":[{"text":"A SAML Authentication Request is initiated by the service provider / client to request the identity provider to authenticate a user. This request is typically generated when a user attempts to access a service that requires authentication and their current session is not authenticated. The request informs the identity provider that a user needs verification and prompts the IdP to either initiate a login process or verify the existing authentication state.","type":"text"}]},{"type":"paragraph","content":[{"text":"The primary purpose of the SAML Authentication Request is to facilitate secure and efficient communication between the service provider and the identity provider and looks something like that:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n \n https://sp.example.com/SAML2\n \n \n \n \n \n urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport\n \n \n","type":"text"}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"SAML Scoping","type":"text"}]},{"type":"paragraph","content":[{"text":"Scoping in the context of SAML is a mechanism used to refine or restrict the processing of authentication and attribute queries. This feature is particularly useful in federated identity environments, where a user's identity and authentication information might be managed across various external identity providers (IdPs). Scoping allows a service provider / client to specify which IdPs should be involved in the authentication process or from where the attributes should be sourced.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Key Elements of SAML Scoping","type":"text"}]},{"type":"paragraph","content":[{"text":"SAML scoping involves several key elements that can be included in an AuthnRequest:","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"ProxyCount","type":"text","marks":[{"type":"code"}]},{"text":": This optional attribute specifies the maximum number of proxying hops that are permitted to occur when processing this request. This feature is currently not yet implemented.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"IDPList","type":"text","marks":[{"type":"code"}]},{"text":": A list of IdPs that are allowed or suggested to be used for handling the request. This is particularly useful in scenarios where the user or the service provider wants to limit which IdPs can respond.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Scoping with IDPList","type":"text"}]},{"type":"paragraph","content":[{"text":"The ","type":"text"},{"text":"IDPList","type":"text","marks":[{"type":"code"}]},{"text":" element within a SAML AuthnRequest specifies the IdPs that are preferred or required for processing the authentication request. It consists of one or more ","type":"text"},{"text":"IDPEntry","type":"text","marks":[{"type":"code"}]},{"text":" elements, each representing an IdP. Each ","type":"text"},{"text":"IDPEntry","type":"text","marks":[{"type":"code"}]},{"text":" includes:","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"ProviderID","type":"text","marks":[{"type":"code"}]},{"text":": The unique identifier of the IdP, which has to match the ","type":"text"},{"text":"authentication scheme","type":"text","marks":[{"type":"code"}]},{"text":" of the ","type":"text"},{"text":"external identity provider","type":"text","marks":[{"type":"link","attrs":{"href":"https://itsense.atlassian.net/l/cp/ZgH1SYxe"}}]},{"text":" in the CoreOne Suite Configuration.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Name","type":"text","marks":[{"type":"code"}]},{"text":": A human-readable name for the IdP, useful in user interfaces.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Loc","type":"text","marks":[{"type":"code"}]},{"text":": An optional attribute that provides a location (URL) where the IdP can be reached.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Example: SAML Authentication Request with Scoping","type":"text"}]},{"type":"paragraph","content":[{"text":"Consider a scenario where a service provider wants to ensure that authentication requests are handled only by specific IdPs. Here is an example of how a SAML AuthN Request with scoping might be structured:","type":"text"}]},{"type":"codeBlock","content":[{"text":"\n \n https://sp.example.com/SAML2\n\n \n \n \n \n \n \n","type":"text"}]},{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"Note: If the client configuration allows for other local authentication methods or other IdPs, only the ones that match the IDPList will be displayed. All other will be discarded.","type":"text"}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Local Provider: cos_local","type":"text"}]},{"type":"paragraph","content":[{"text":"If you also want to allow any of the configured and available local authentication methods, you can pass along the following ","type":"text"},{"text":"IDPEntry","type":"text","marks":[{"type":"code"}]},{"text":" in the AuthnRequst:","type":"text"}]},{"type":"codeBlock","content":[{"text":"","type":"text"}]},{"type":"paragraph"}],"version":1}