Microsoft WS-I Basic Security Profile 1.0 Sample Application

You may ignore the basic profiles 1.1 conformance setting the ConformsTo property to WsiProfiles.None or the EmitConformanceClaims property to false programmatically. It is possible to configure the application for the same purpose as shown in Listing 2.

Improvements to logging and error handling, profile implementations now throw exceptions which are logged inside filter objects and fail with ServletExceptions, sample application newly shows handling of these errors

Modify filesample/src/main/webapp/WEB-INF/securityContext.xmlof the sample application, replace metadataGeneratorFilter bean as follows and make sure to replacethe entityId value with a string which is unique within the SSO Circle service (e.g. urn:test:yourname:yourcity):

Configuration of the SAML library requires beans definitions included in thesample/src/main/webapp/WEB-INF/securityContext.xmlconfiguration file. Include copy of the file in your own Spring application, either directly or withan inclusion. Configuration steps in the following chapters will be customizing beans included inthe default context.

Open the Spring SAML sample application at e.g. :8443/spring-security-saml2-sample, select your AD FS server and press login. In case Artifact bindingis used and SSL/TLS certificate of your AD FS is not already trusted, import it to your samlKeystore.jks by following instructions in theerror report.

Open the Spring SAML sample application at e.g. :8080/spring-security-saml2-sample, select your Okta server and press login. Alternatively start IDP-initializedsingle sign-on using App Embed Link provided by Okta in application configuration, e.g. _springsaml_1/0oa4vkeakAsUtZ8AI0y6/39139. 2b1af7f3a8