- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I have implemented the SASWebserver hotfix https://tshf.sas.com/techsup/download/hotfix/HF2/M1V.html and I started receiving the error "The application is not authorized to use SAS Logon Manager." for SASStudio and SASEnvironment manager.
Tried implementing https://support.sas.com/kb/56/451.html for EVM and still same issue. Any suggestions on this?.
2024-06-05 14:17:33,796 [tomcat-http--27] ERROR org.apereo.cas.support.rest.resources.ServiceTicketResource - NullPointerException
RegisteredServiceAccessStrategyUtils.java:ensureServiceSsoAccessIsAllowed:107
DefaultCentralAuthenticationService.java:get:110
DefaultCentralAuthenticationService.java:get:102
2024-06-05 14:17:34,014 [tomcat-http--28] WARN org.apereo.cas.authentication.attribute.PrincipalAttributeRepositoryFetcher - No person records were fetched from attribute repositories for [{principal=sasadm, credentialClass=[UsernamePasswordCredential], credentialId=[sasadm@saspw], username=sasadm@saspw}]
2024-06-05 14:17:34,015 [tomcat-http--28] INFO org.apereo.cas.authentication.DefaultAuthenticationManager - Authenticated principal [sasadm@saspw] with attributes [{}] via credentials [[UsernamePasswordCredential(username=sasadm@saspw, source=null, customFields={})]].
2024-06-05 14:17:34,035 [tomcat-http--29] ERROR org.apereo.cas.services.web.support.RegisteredServiceResponseHeadersEnforcementFilter - Service unauthorized
RegisteredServiceAccessStrategyAuditableEnforcer.java:lambda$execute$6:200
Optional.java:orElseGet:369
RegisteredServiceAccessStrategyAuditableEnforcer.java:execute:194
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
The error message seems to be saying that SASLogon can't pull this information, so I would expect this to fail for every service.
Typically this "application is not authorized..." message occurs when the redirect URI (e.g. hostname:7443/, hostname:8343/SASStudio) does not exist in Metadata.
In SAS Management Console > Application Management > Configuration Manager > SAS Application Infrastructure, confirm in the properties for the DP-SAS-Environment-Manager and SAS Studio Mid-Tier properties the Internal and External Connection tabs have the correct information.
If those are correct (or the failure is for all applications), you might need to rebuild / redeploy your web applications.
Greg Wootton | Principal Systems Technical Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I suggest you open a Tech Support track for this if you haven't already.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
The error message seems to be saying that SASLogon can't pull this information, so I would expect this to fail for every service.
Typically this "application is not authorized..." message occurs when the redirect URI (e.g. hostname:7443/, hostname:8343/SASStudio) does not exist in Metadata.
In SAS Management Console > Application Management > Configuration Manager > SAS Application Infrastructure, confirm in the properties for the DP-SAS-Environment-Manager and SAS Studio Mid-Tier properties the Internal and External Connection tabs have the correct information.
If those are correct (or the failure is for all applications), you might need to rebuild / redeploy your web applications.
Greg Wootton | Principal Systems Technical Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thank you @gwootton : Rebuilding and deploy web applications worked. Not sure what actually caused this issue. There were not changes other than the mentioned hotfix and the current one doesn't list rebuild as a requirement.