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.
SVNResourceConfiguration
This is deprecated and will be removed in the V4 release
The resource:SVNResource
type allows access to data which is stored in an SVN repository.
Configuring the SVNResource
Licensing constraints mean that the required jars cannot be bundled with the Shibboleth distribution and so, prior to configuring an SVN resource, you need to download the SVNKit jar from into %{idp.home}/edit-webapp/WEB-INF/lib and rebuild and deploy the war file.
Examples
<MetadataResource xmlns:resource="urn:mace:shibboleth:2.0:resource" xsi:type="resource:SVNResource" resourceFile="entity.xml" repositoryURL="https://svn.example.org/repo/path/to.dir" workingCopyDirectory="%{idp.home}/metadata/svn" />
Schema Names and location
The resource: prefix is defined by the urn:mace:shibboleth:2.0:resource
schema which can be located at http://shibboleth.net/schema/idp/shibboleth-resource.xsd.
Attributes
Name | Type | Default | Description |
---|---|---|---|
| URL | required | The URL of the directory within the SVN repository. svn, svn+ssh, http(s) are supported |
| Local directory name | required | The name of a local directory into which the repository directory will be unpacked. This directory will be created if it doesn't exist |
| File name | required | The file name to be used |
| String | user name used to authenticate to the remote repository | |
| String | password used to authentication to the remote repository | |
| String | HTTP proxy used through which HTTP/HTTPS connections will be sent | |
| String | HTTP proxy port used through which HTTP/HTTPS connections will be sent | |
| String | Username to be presented at the HTTP proxy | |
| String | Password to be presented at the HTTP proxy |
Child Elements
No Child Elements should be specified. Any child elements will be ignored.
Related Topic
The same underlying code is used when define top level configuration to be loaded from SVN. See SVNResource