Federation Manager Release Notes › Known Issues › Partnership and Entity Issues › HTTP-Artifact Requires Encrypted Assertion with Non-ASCII Characters (98479)

Previous Topic: Spaces Not Allowed in Partnership Names (74945)

Next Topic: SAML 1.1 SSO Fails if LDAP Search Specification Uses NameID (101493)

HTTP-Artifact Requires Encrypted Assertion with Non-ASCII Characters (98479)

If you are using HTTP-Artifact as the binding for single sign-on and the assertion contains non-ASCII characters, encrypt the assertion or check that the artifact back channel is an SSL connection.

Copyright © 2010 CA. All rights reserved. Email CA about this topic