Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 116: | Line 116: | ||
<ul> | <ul> | ||
<li>'''issuer''': The SAML IDP URI that you created in the PureCloud Provisioning steps above (for example: <nowiki>https://www.genesys.com/pureengage</nowiki>).</li> | <li>'''issuer''': The SAML IDP URI that you created in the PureCloud Provisioning steps above (for example: <nowiki>https://www.genesys.com/pureengage</nowiki>).</li> | ||
| − | <li>'''certificate''': The public key of the SAML related certificate (a base64 PEM encoded key).</li> | + | <li>'''certificate''': The public key of the SAML related certificate (a base64 saml.pem PEM encoded key).</li> |
| − | <li>'''pkey''': The encrypted SAML related certificate private key (a private key encrypted in aes256 with a password (see password option below) and encoded in base64).</li> | + | <li>'''pkey''': The encrypted SAML related certificate private key (a saml.pkcs8 private key encrypted in aes256 with a password (see password option below) and encoded in base64).</li> |
<li>'''password''': The password to decrypt the private key.</li> | <li>'''password''': The password to decrypt the private key.</li> | ||
<li>'''expire_time''': The expiration time (in hours) for the access token. The default is 24 hours. This might be overridden on the server side.<br> | <li>'''expire_time''': The expiration time (in hours) for the access token. The default is 24 hours. This might be overridden on the server side.<br> | ||
| Line 130: | Line 130: | ||
openssl rsa -in key.pem -out key_protected.pem -aes256openssl base64 -in key_protected.pem -out result _file_name | openssl rsa -in key.pem -out key_protected.pem -aes256openssl base64 -in key_protected.pem -out result _file_name | ||
</source> | </source> | ||
| + | Once you have created the two PEM files perform the following steps: | ||
| + | <ul> | ||
| + | <li>Encode saml.pem into a base64 string (=>’saml.pem.b64’) using this command: | ||
| + | <source lang="text"> | ||
| + | openssl base64 -in saml.pem -out saml.pem.b64 | ||
| + | </source> | ||
| + | </li> | ||
| + | <li>Encrypt the saml.pkcs using a password (=>’saml.pkcs.enc.password’) and then encode the resulting content into a base64 string (=>’saml.pkcs.enc.b64’) using this command: | ||
| + | <source lang="text"> | ||
| + | openssl rsa -in saml.pkcs8 -out saml.pkcs8.enc -aes256 | ||
| + | </source> | ||
| + | (specify the value of saml.pkcs.enc.password when prompted) | ||
| + | <source lang="text"> | ||
| + | openssl base64 -in saml.pkcs8.enc -out saml.pkcs8.enc.b64 | ||
| + | </source> | ||
| + | </li> | ||
| + | </ul> | ||
| + | The resulting material can be set in the saml section of the transaction object: | ||
| + | <ul> | ||
| + | <li>certificate=<saml.pem.b64></li> | ||
| + | <li>pkey=<saml.pkcs.enc.b64></li> | ||
| + | <li>password=<saml.pkcs.enc.password></li> | ||
| + | </ul> | ||
</li> | </li> | ||
</ul> | </ul> | ||
Revision as of 14:59, May 29, 2019
This is a draft page; the published version of this page can be found at PEC-Hybrid/Current/Admin/About.
Contents
This article describes the essential provisioning steps to enable a hybrid integration between PureEngage On-Prem deployments and Genesys PureCloud services.