Modifying PRAuth login screen
Changes done to the webwb/py-login-screen.css and stored in an unauthenticated ruleset is not loaded when accessing /prweb/PRAuth login screen. It works fine for /prweb Changes made to pyDisplayAuthScreenSelector stored in the same ruleset are shown in /prweb/PRAuth How chan I make the /prweb/PRAuth use the same .css as /prweb
Updated: 13 Apr 2023 8:42 EDT
Tata Consultancy Services
IN
Hi @TorIngeV
You want customize the login screen instead of the pega login screen?
for that you need modify the below rules and add into your local ruleset.
Rule Type: HTML
Rule Name:Web-Login
CL:@baseclass
This rule is used to change the Pega Logo from the login screen
----------------------------------------------------------------------------------------------------------------
Rule Type: Text File: login-screen
Rule Name:webwb py-login-screen css
This rule is used to change the background login screen
----------------------------------------------------------------------------------------------------------------
Rule Type: Access Group: AccessGroupName
We have create a new access group
----------------------------------------------------------------------------------------------------------------
RuleType:Requestor Type: BROWSER Starting connection
RuleName: pega • BROWSER
In this rule you have to change default access group to your access group.
----------------------------------------------------------------------------------------------------------------
I hope this will help you.
Thanks,
Ashok
Equinor
NO
@BhumireddyI have customized the login screen, and it is working perfectly when using /prweb and logging in with locally defined operators. The challenge is when accessing /prweb/PRAuth in order to use a federated authentication service. Then it does not pull the same weblogin or css files as /prweb does. As mentioned in my original post if I modify the pyDisplayAuthScreenSelector used by /prweb/PRAuth and store the changes in the same ruleset as used by the customized login for /prweb it uses the modified code.
Endeavour Energy
AU
@TorIngeV When Pega is forming the oauth url path(oauth2/v1/webwb/) to access resources for some reason its not able to access the changes stored in unauthenticated ruleset
Workaround is to specify the relative path
So instead of below in pyDisplayAuthScreenSelector
<link rel='stylesheet' type='text/css' href='<%=imageRestPath%>py-login-screen.css' /> <link rel='stylesheet' type='text/css' href='<%=imageRestPath%>py-login-screen-auth-providers.css' /> <link rel='stylesheet' type='text/css' href='<%=imageRestPath%>py-CAPTCHA-div.css' />
Change it to
<link rel='stylesheet' type='text/css' href='webwb/py-login-screen.css' /> <link rel='stylesheet' type='text/css' href='webwb/py-login-screen-auth-providers.css' /> <link rel='stylesheet' type='text/css' href='webwb/py-CAPTCHA-div.css' />
which will resolve the issue but impacts arent clear
Would be good to understand why the oauth2/v1/webwb/ reference doesn't work for the updates if you were able to resolve this via any other approach please do share
HealthFirst Org
US
I am also facing the same issue. Are you able to find the root cause of the issue ?