This guide will describe how to get Shibboleth 3.2.x working with Kiteworks (aka Accellion). Currently the vendor does not have documentation on this integration, here is how I got it working.
In the code below:
Replace SPName with the name you provide within the Kiteworks UI (shown below).
----------
<MetadataProvider id="SPName" xsi:type="FilesystemMetadataProvider" xmlns="urn:mace:shibboleth:2.0:metadata" metadataFile="%{idp.home}/metadata/SPName.xml" failFastInitialization="false" /> |
Note: metadata generated from the appliance will expire, ensure to remove the validUntil and cacheDuration entries within the metadata file.
<bean parent="RelyingPartyByName" c:relyingPartyIds="SPName"> <property name="profileConfigurations"> <list> <bean parent="SAML2.SSO" p:encryptAssertions="false" /> </list> </property> </bean> |
<bean parent="shibboleth.SAML2AttributeSourcedGenerator" p:format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" p:attributeSourceIds="#{ {'mail'} }"> <property name="activationCondition"> <bean parent="shibboleth.Conditions.RelyingPartyId" c:candidate="SPname" /> </property> </bean> |
<AttributeFilterPolicy id="SPName"> <PolicyRequirementRule xsi:type="OR"> <Rule xsi:type="Requester" value="SPName" /> </PolicyRequirementRule> <AttributeRule attributeID="mail"> <PermitValueRule xsi:type="ANY" /> </AttributeRule> </AttributeFilterPolicy> |