[[DocuSign]]
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
docpublic:systemes:shibboleth:docusign [2021/01/28 14:58] procacci@tem-tsp.eu [Mail rewriting] |
docpublic:systemes:shibboleth:docusign [2023/10/24 14:46] (current) adminjp [shib IDP attribute-resolver] |
||
|---|---|---|---|
| Line 38: | Line 38: | ||
| {{: | {{: | ||
| - | We also set thet we use signe AuthN an use Post Method . | + | We also set that we use signed |
| ==== DocuSign SP Metadata ==== | ==== DocuSign SP Metadata ==== | ||
| Line 60: | Line 60: | ||
| === SP metadata certificate === | === SP metadata certificate === | ||
| - | the ducosing | + | the DocuSign |
| get certificate from SP metadata element X509Certificate : | get certificate from SP metadata element X509Certificate : | ||
| Line 229: | Line 229: | ||
| ===== shib IDP attribute-resolver ===== | ===== shib IDP attribute-resolver ===== | ||
| - | In the IDP we use the **attribute-resolver-ldap.xml** file to define our customized for DocuSign for NameID mail attribute and permission (employeeType) | + | In the IDP we use the **attribute-resolver-ldap.xml** |
| < | < | ||
| [root@idptest conf]# grep attribute-resolver-ldap.xml services.xml | [root@idptest conf]# grep attribute-resolver-ldap.xml services.xml | ||
| < | < | ||
| - | </ | + | </ |
| + | |||
| + | ==== mapped attributes ==== | ||
| + | |||
| + | in order to map DocuSign domains ID to our mail domains we need to map values | ||
| + | |||
| + | attribute-resolver.xml mapped employeType | ||
| + | |||
| + | < | ||
| + | < | ||
| + | |||
| + | < | ||
| + | < | ||
| + | <!-- Values Prod --> | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | ... | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | idem for staticDSAccountID | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | name=" | ||
| + | < | ||
| + | <!-- Values DocuSign Prod --> | ||
| + | <!-- < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | ... | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | </ | ||
| ==== Mail rewriting ==== | ==== Mail rewriting ==== | ||
| Line 265: | Line 324: | ||
| when a user connect with it's email address of givenName.Surname@**domain2**.eu , it is finally transmited to DocuSign SP as givenName.Surname@**domain1**.eu . | when a user connect with it's email address of givenName.Surname@**domain2**.eu , it is finally transmited to DocuSign SP as givenName.Surname@**domain1**.eu . | ||
| + | ==== Permission map ==== | ||
| + | We also used a mapped attribute definition in oder to match Roles/ | ||
| + | |||
| + | < | ||
| + | < | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | ==== static AttributeDefinition for AccountID ==== | ||
| + | |||
| + | DocuSign support told us also to send a static value for the accoundID so that automatic profile affectation could be done | ||
| + | |||
| + | we can get our API account ID from the E-Signature parameter screen , left menu => API-Keys | ||
| + | |||
| + | {{: | ||
| + | |||
| + | then we need our IDP to map and send that static value for everyone, so we creted a staticDataconnector and the associated decated static AttributeDefinition for thos DocuSign authZ feature with the creation of a custom staticDSAccountID attribute : | ||
| + | |||
| + | references : | ||
| + | |||
| + | * https:// | ||
| + | * https:// | ||
| + | |||
| + | in conf/ | ||
| + | |||
| + | < | ||
| + | |||
| + | < | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | name=" | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | ==== Special case when unsing NAT ( checkAddress=" | ||
| + | |||
| + | clients in specific site which don't have many public IPs addresses use NAT , and it breaks the flow of using a proxied IDP | ||
| + | In that case we must disable " | ||
| + | |||
| + | Analagous to the SP, there' | ||
| + | |||
| + | https:// | ||
| + | |||
| + | |||
| + | from examples in the doc: | ||
| + | * https:// | ||
| + | I understand that I can specify the checkAddress attribute only for those "2nd Hand/ | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | < | ||
| + | < | ||
| + | <bean parent=" | ||
| + | </ | ||
| + | </ | ||
