BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
mkiran
Quartz | Level 8

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?.

 
Web/Logs/SASServer1_1/SASLogon9.4.log
 

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

 

 
2024-06-05 16:25:01,254 [tomcat-http--43] ERROR org.apereo.cas.services.web.support.RegisteredServiceResponseHeadersEnforcementFilter - Service unauthorized
RegisteredServiceAccessStrategyAuditableEnforcer.java:lambda$execute$6:200
Optional.java:orElseGet:369
RegisteredServiceAccessStrategyAuditableEnforcer.java:execute:194
 
2024-06-05 16:25:01,254 [tomcat-http--43] ERROR org.apereo.cas.support.rest.resources.ServiceTicketResource - NullPointerException
RegisteredServiceAccessStrategyUtils.java:ensureServiceSsoAccessIsAllowed:107
DefaultCentralAuthenticationService.java:get:110
DefaultCentralAuthenticationService.java:get:102
 
 

mkiran_0-1717618971095.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
gwootton
SAS Super FREQ
Does this happen for other applications or only those two?

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

View solution in original post

3 REPLIES 3
SASKiwi
PROC Star

I suggest you open a Tech Support track for this if you haven't already.

gwootton
SAS Super FREQ
Does this happen for other applications or only those two?

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
mkiran
Quartz | Level 8

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.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 309 views
  • 1 like
  • 3 in conversation