[Shib-Users] transientid vs long restart

[Janusz Ulanowski]

Hi guys,


When I have enabled
----------------------------------
<resolver:AttributeDefinition id="transientId"
xsi:type="TransientId" xmlns="urn:mace:shibboleth:2.0:resolver:ad">
<resolver:AttributeEncoder xsi:type="SAML1StringNameIdentifier"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
nameFormat="urn:mace:shibboleth:1.0:nameIdentifier" />
<resolver:AttributeEncoder xsi:type="SAML2StringNameID"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"

nameFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:transient" />
</resolver:AttributeDefinition>
-------------------------------------------
then staring tomcat takes about 30seconds longer . Attached log : The
last line is just before long gap (30seconds).
Is normal behaviour?
Thanks,
-----------------------------------------
14:04:29.454 - TRACE
[edu.internet2.middleware.shibboleth.common.config.BaseSpringNamespaceHandler:108]
- Attempting to find parser for element of type:
{urn:mace:shibboleth:2.0:attribute:encoder}SAML2StringNameID
14:04:29.456 - TRACE
[edu.internet2.middleware.shibboleth.common.config.BaseSpringNamespaceHandler:108]
- Attempting to find parser for element of type:
{urn:mace:shibboleth:2.0:resolver:ad}TransientId
14:04:29.456 - INFO
[edu.internet2.middleware.shibboleth.common.config.attribute.resolver.AbstractResolutionPlugInBeanDefinitionParser:54]
- Parsing configuration for AttributeDefinition plugin with ID: transientId
14:04:29.457 - DEBUG
[edu.internet2.middleware.shibboleth.common.config.attribute.resolver.AbstractResolutionPlugInBeanDefinitionParser:60]
- Setting the following attribute definition dependencies for plugin
transientId: null
14:04:29.457 - DEBUG
[edu.internet2.middleware.shibboleth.common.config.attribute.resolver.attributeDefinition.BaseAttributeDefinitionBeanDefinitionParser:57]
- Setting source attribute ID for attribute definition transientId to:
14:04:29.457 - DEBUG
[edu.internet2.middleware.shibboleth.common.config.attribute.resolver.attributeDefinition.BaseAttributeDefinitionBeanDefinitionParser:81]
- Attribute definition transientId produces attributes that are only
dependencies: false
14:04:29.457 - TRACE
[edu.internet2.middleware.shibboleth.common.config.BaseSpringNamespaceHandler:108]
- Attempting to find parser for element of type:
{urn:mace:shibboleth:2.0:attribute:encoder}SAML1StringNameIdentifier
14:04:29.459 - TRACE
[edu.internet2.middleware.shibboleth.common.config.BaseSpringNamespaceHandler:108]
- Attempting to find parser for element of type:
{urn:mace:shibboleth:2.0:attribute:encoder}SAML2StringNameID
--------------------------------------



--
Janusz Ulanowski

[Chad La Joie]

It can be. The transient ID attribute definition has to start up the
random number generator for the system. In some cases, depending on the
OS (in particular Windows) and JVM (in particular IBM's JVM) this can
take a while.

Chad La Joie
www.itumi.biz
trusted identities, delivered

[Janusz Ulanowski]

Thank you Chad,
now it's clear to me:)

Janusz Ulanowski

[Chad La Joie]

I guess the other thing to note is that if that is the cause of the
pause, remove the transient ID attribute definition does not, in fact,
make the pause go away, it just postpones it. The same random number
generator is used for things like creating the Assertion IDs.

[Janusz Ulanowski]

you're right I can see that now.
Thanks for clarify it.