Question
Mitsubishi HC Capital Inc.
JP
Last activity: 4 Sep 2023 21:53 EDT
We'd like to use hyphen(-) character in operator ID strings.
According to your document, We are not allowed to use hyphen(-) character in operator ID strings.
「In addition to letters and digits, the identifier can include the following characters: period (.), single quote ('), tilde (~), underscore (_), exclamation point (!), ampersand (&), octothorpe (#) and no more than one at (@) character. Avoid using the forward slash (/) or backslash (\) characters in the identifier.」
Creating an operator ID (pega.com)
However, We are using "XXX-YYY-ZZZ.com" as mail domain. So, I'd like to ask to relax your restriction, and accept hyphen(-) character in operator ID strings.
Updated: 8 Aug 2023 8:03 EDT
Pegasystems Inc.
GB
@tyamamushi I had a look at your question and found this post: A hyphen in Operator ID
I checked on status of the mentioned enhancement request, FDBK-5918 (Allow embedded hyphens in operator ids) but it is closed. In the process of my research found some other enhancements request made for this functionality:
Support hyphenated names for Operator ID's (FDBK-11786)
Unable to create an Operator Id with hyphen(-) Symbol (FDBK-99875)
These all culminated into the following Enhancement ticket: Support hyphenated names for Operator ID's (US-100245) but this was withdrawn and closed.
Pega released two support articles for this problem:
1. Special characters in Operator ID (SA-16276)
Workaround:
A local-change that can avoid this issue is to use an authentication activity that translates hyphens "-" in the AD logon credentials provided by a user in to an allowed character such as an underscore "_" to arrive at the Pega Operator ID.
2. Issue with creating operator ID with a hyphen (SA-10600)
@tyamamushi I had a look at your question and found this post: A hyphen in Operator ID
I checked on status of the mentioned enhancement request, FDBK-5918 (Allow embedded hyphens in operator ids) but it is closed. In the process of my research found some other enhancements request made for this functionality:
Support hyphenated names for Operator ID's (FDBK-11786)
Unable to create an Operator Id with hyphen(-) Symbol (FDBK-99875)
These all culminated into the following Enhancement ticket: Support hyphenated names for Operator ID's (US-100245) but this was withdrawn and closed.
Pega released two support articles for this problem:
1. Special characters in Operator ID (SA-16276)
Workaround:
A local-change that can avoid this issue is to use an authentication activity that translates hyphens "-" in the AD logon credentials provided by a user in to an allowed character such as an underscore "_" to arrive at the Pega Operator ID.
2. Issue with creating operator ID with a hyphen (SA-10600)
One of the reasons for the limitation could be Pega class names contains hyphen so Pega does not allow hyphen "-". In addition to hyphen "-", Pega does not support "+", "$", etc.
Workaround:
Please can you try the suggestion provided in the PSC post?
"It seems the special character check against the operator id only happens if you create a new operator record using the new form of data-admin-operator-id.
I found it is possible to create an operator id contains hyphen by running an activity which copies existing operator id and set the pyUserIdentifier to a new value."
ie
The operators can't be created with special characters with Hyphens as OOTB. There are only limited special characters allowed as given in below screenshot.
However, the SSO authenitcation uses model operator from third party application which is IdP and the IdP credentials are passed at runtime to authenticate into Pega application. So, the authentication activity can create operator with Hyphens(-) as part of authentitcation from IdP.
See SA-16276 for the steps.
@tents @pageb Brian, as SME of Dev Studio / Operator Management could you provide some input on this question? Are there plans to incorporate FDBK-99875 into a future version?
Could the steps provided in the archived support articles be included in the main documentation Creating an operator ID?
Mitsubishi HC Capital Inc.
JP
Thank you for your reply.
We consider using other attributes of our IdP as strings for the pega operator ID.