Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 148: | Line 148: | ||
<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). You must encrypt the private key with a password that you create before you store the key in Config Server.</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). You must encrypt the private key with a password that you create before you store the key in Config Server.</li> | ||
<li>'''password''': The password to decrypt the private key. You must store the password in the '''password''' option. You can use OpenSSL to perform the encryption with your password</li> | <li>'''password''': The password to decrypt the private key. You must store the password in the '''password''' option. You can use OpenSSL to perform the encryption with your password</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.< | + | <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.</li> |
| + | </ul> | ||
The resulting material can be set in the saml section of the transaction object: | The resulting material can be set in the saml section of the transaction object: | ||
<ul> | <ul> | ||
| Line 154: | Line 155: | ||
<li>pkey=<saml.pkcs.enc.b64></li> | <li>pkey=<saml.pkcs.enc.b64></li> | ||
<li>password=<saml.pkcs.enc.password></li> | <li>password=<saml.pkcs.enc.password></li> | ||
| − | |||
| − | |||
</ul> | </ul> | ||
To allow for better control and monitoring of the components using PureCloud Services, for each PureEngage Service that uses a common service you must create multiple sections, one for each OAuth client, in Configuration Server to allow for better control and monitoring of the components using the PureCloud Services and for different rate limiting per client. This does not mean that if you have ''n'' number of components on premises that are associated with one another, they cannot share a given client id.<br /> | To allow for better control and monitoring of the components using PureCloud Services, for each PureEngage Service that uses a common service you must create multiple sections, one for each OAuth client, in Configuration Server to allow for better control and monitoring of the components using the PureCloud Services and for different rate limiting per client. This does not mean that if you have ''n'' number of components on premises that are associated with one another, they cannot share a given client id.<br /> | ||
Revision as of 15:22, May 30, 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.