Skip to content

Tag: saml

Why is this XML Validation failing on NameIDFormat from an extended type?

I recently encountered an issue with SAML metadata validation from a customer. The relevant part of metadata that is failing: This fails with the folowing error: cvc-complex-type.2.4.a: Invalid content was found starting with element ‘NameIDFormat’. One of ‘{“urn:oasis:names:tc:SAML:2.0:metadata”:SingleSignOnService, “urn:oasis:names:tc:SAML:2.0:metadata”:NameIDMappingService, “urn:oasis:names:tc:SAML:2.0:metadata”:AssertionIDRequestService, “urn:oasis:names:tc:SAML:2.0:metadata”:AttributeProfile, “urn:oasis:names:tc:SAML:2.0:assertion”:Attribute}’ is expected. The following is the relevant portion of saml-schema-metadata-2.0.xsd: I notice that the error message only specifies

SAML – Get attributes from client side or Java ee REST api

I need to get attributes of the account from SAML identity provider. Is there any way to do it from client-side (javascript, browser) or using java ee REST API(JAX-RS)? I have found many tutorials about using SAML but they always describe a process of authorization application(always use server-side and jsp/jsf). I don’t need it. I just want to read attributes

How to create a SSO Service Provider?

I am new to the concept of Single Sign On. We already have a Java web application which manages its user. Now the requirement is that the authentication will be provided by the SSO Idp at customer end (using SAML) after which the request will be forwarded to our application. Since I haven’t implemented anything like this before, I need