-
I'm working on a PR to fix this issue and any others that crop up in the debugging process. Currently it looks like I'll need to check during `get()` calls if `key.contentEquals("oidcStateAttribute")`…
-
I am struggling a bit setting up SP-initiated single logout with Owin.
My Idp exposes the logout endpoint like this:
```xml
```
I have set up authservices to load the metadata from the metadata …
-
Instructions for using with Shibboleth:
https://wiki.library.ucsf.edu/pages/viewpage.action?pageId=361762610
CMU's Instructions:
https://www.cmu.edu/computing/security/authentication/web-login/sh…
-
I'm trying to enable SSO through SAMLv2 with Azure Active Directory as the identify provider. I'm facing a few issues with release 1.3.
First, under authentication methods, once I'm done configurin…
-
I am trying to new package with identityserver2 but still not succeeded to pass.
When I am trying to open a restricted path, It is redirected to the follownig endpoint in my IdP issue/wstrust/mixed…
-
-
In DefaultSAMLTokenProvider, the SecurityTokenReference elements are created
with wrong ValueTypes when the requested token is of type
[http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#…
-
com.sun.xml.ws.security.trust.impl.IssueSamlTokenContractImpl checks for valid
token types, but
"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0" is
not recognized as a SAML 2…
-
This is probably related to issue 206: When including an issued SamlToken in a
message, and sp:ProtectTokens is set, the generated signature will reference an
unknown element, for example
Caused by: …
-
Trust Functional
Scenario s99
description - Symmetric binding with TokenType = SAML20 as IssuedToken ( here IssuedToken is taken as ProtectionToken ) with WSTrustContractImpl
Soap Log
========
Dec 9…