The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

Current File(s): conf/services.xml, services.properties

Format: Native Spring

Legacy V2 File(s): conf/services.xml

The services.xml file is used to specify many of the other configuration files (or more generally, Spring Resources) to load to configure various important services within the IdP. The services.properties file provides a less granular way to identify the Spring beans containing the lists of resources, and also controls the dynamic reloading behavior of those services.

You might modify these files to:

  • change the resources used, or more commonly add additional resources to supplement built-in defaults
  • configure more specialized approaches such as Subversion resources or remote HTTP resources
  • control how often to check for changes and reload configurations, if at all

V2 Compatibility

A similar function was performed by the services.xml file in 2.x, but in 3.0 this file is now a native Spring bean file and the older services XML schema is not supported or used.

Overview

The services.xml file contains a series of "list" beans that specify the Spring Resources to load into various services. The lists are named with specific bean IDs (see below) that direct the resources into the various services. If you wish to supply your own resource lists without modifying the delivered lists, you may control the bean IDs used by modifying services.properties.

Do not remove any of the beans from services.xml unless you alter a corresponding property in services.properties to direct the service to a different resource list bean, or the IdP will fail to initialize with an error referencing the missing bean.

Beans

Beans defined in services.xml follow:

Bean IDTypeFunctionReloadable Service ID
shibboleth.RelyingPartyResolverResourcesjava.uti.ListRelyingPartyConfiguration resources for a new or migrated installation.shibboleth.RelyingPartyResolverService
shibboleth.LegacyRelyingPartyResolverResourcesjava.uti.ListRelyingPartyConfiguration using a deprecated V2 relying-party.xml file.shibboleth.RelyingPartyResolverService
shibboleth.MetadataResolverResourcesjava.uti.ListMetadataConfiguration resources.shibboleth.MetadataResolverService
shibboleth.AttributeResolverResourcesjava.uti.ListAttributeResolverConfiguration resources.shibboleth.AttributeResolverService
shibboleth.AttributeFilterResourcesjava.uti.ListAttributeFilterConfiguration resources.shibboleth.AttributeFilterService
shibboleth.NameIdentifierGenerationResourcesjava.uti.ListNameIDGenerationConfiguration resources.shibboleth.NameIdentifierGenerationService
shibboleth.AccessControlResourcesjava.uti.ListAccessControlConfiguration resources.shibboleth.ReloadableAccessControlService
shibboleth.MessageSourceResourcesjava.uti.ListInternationalizable user interface messages.N/A

Properties

Properties defined in services.properties follow:

PropertyDefaultFunction
idp.service.logging.resource%{idp.home}/conf/logback.xml 
idp.service.logging.failFastfalse 
idp.service.logging.checkInterval0 
   
idp.service.relyingparty.resourcesshibboleth.RelyingPartyResolverResources 
idp.service.relyingparty.failFastfalse 
idp.service.relyingparty.checkInterval0 
   
idp.service.metadata.resourcesshibboleth.MetadataResolverResources 
idp.service.metadata.failFastfalse 
idp.service.metadata.checkInterval0 
   
idp.service.attribute.resolver.resourcesshibboleth.AttributeResolverResources 
idp.service.attribute.resolver.failFastfalse 
idp.service.attribute.resolver.checkInterval0 
   
idp.service.attribute.filter.resourcesshibboleth.AttributeFilterResources 
idp.service.attribute.filter.failFastfalse 
idp.service.attribute.filter.checkInterval0 
   
idp.service.nameidGeneration.resourcesshibboleth.NameIdentifierGenerationResources 
idp.service.nameidGeneration.failFastfalse 
idp.service.nameidGeneration.checkInterval0 
   
idp.service.access.resourcesshibboleth.AccessControlResources 
idp.service.access.failFastfalse 
idp.service.access.checkInterval0 
   
idp.message.resourcesshibboleth.MessageSourceResources 
idp.message.cacheSeconds300 
   

idp.httpclient.connectionDisregardTLSCertificate

false 
idp.httpclient.connectionTimeout-1 
idp.httpclient.memorycaching.maxCacheEntries50 
idp.httpclient.memorycaching.maxCacheEntrySize1048576 
idp.httpclient.filecaching.maxCacheEntries100 
idp.httpclient.filecaching.maxCacheEntrySize10485760 

idp.httpclient.filecaching.cacheDirectory

None 

Advanced Notes

You can use any kind of Resource supported by Spring, along with additional custom resource types provided with the IdP for handling Subversion, HTTP, and file-backed HTTP resources.

 

  • No labels