[jboss-identity-issues] [JBoss JIRA] Created: (JBID-137) JBoss STS - improve the configuration to allow for general properties to be specified for each token provider

JBoss STS - improve the configuration to allow for general properties to be specified for each token provider ------------------------------------------------------------------------------------------------------------- Key: JBID-137 URL: https://jira.jboss.org/jira/browse/JBID-137 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha3 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDFED-1.0.0.alpha4 JBoss STS does not currently provide a way to specify general properties for a token provider. A token provider may be configurable (for example, a provider may take an URL of a third-party service or repository) and the configuration schema must be changed to allow the specification of properties. The token providers should also be associated with the token element (namespace and local name) besides the token type. The reason for doing this is that validation/renewing/cancellation requests do not specify the token type explicitly so it must be inferred by the token element. The only way for the STS to figure out which provider should be used to validate the token is by having an association between token elements and providers. Something like: <TokenProvider ProviderClass="...." TokenType="..." TokenNamespace="urn:...." TokenName="Assertion"> <Property name="..." value="..."/> <Property name="..." vluae="..."/> </TokenProvider> A final note about configuration is about the need for the TruststoreAlias attribute of the ServiceProvider. The alias of each service provider can be configured through the ValidatingAlias element of KeyProvider, so we may just make the TruststoreAlias attribute optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira