Hi,
After deploying SAS Viya 3.4 and reset the password for sasboot, I encountered the following error:
The application is not authorized to use SAS Logon Manager.
I would appreciate any pointer or advice on how to resolve this issue.
Thanks in advance.
Have you noticed that your hostname doesn’t match what’s in the certificate? i.e. sasviyaV34 vs sasviya34 The hostname has an extra V.
Hello @S_S,
what application do you try to access? SASHome? SASEnvironmentManager?
I suggest to give a look to the logs of saslogon-default micro-service, it will most probably provide more details.
I just deployed SAS Viya 3.4. I have only managed to reset the password for sasboot and after that it return me the error.
The log file output as follow:
2018-11-19 16:07:45.306 ERROR 14786 --- [n Asynchronous5] c.s.c.bootstrap.ConfigurationLoader : service [d710504ae02a058e] [CONFIGURATION_BOOTSTRAP_RESTCLIENT_EXCEPTION] POST encountered an exception attempting to invoke the [HTTPMethod=com.sas.configuration.bootstrap.ConfigurationLoader@6f8ac8d5][endPoint=/configuration/definitions]
2018-11-19 16:07:47.126 WARN 14786 --- [n Asynchronous2] c.s.a.bootstrap.RemoteRuleLoader : service [736bb64ec4def0a8] [RETRIEVAL_EXCEPTION] An exception occurred while retrieving the existing rules: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "/authorization/rules": Certificate for <SASVIYAV34.ndblab.local> doesn't match any of the subject alternative names: [SASVIYA34, SASVIYA34.ndblab.local, SASVIYA34, SASVIYA34, *.SASVIYA34.ndblab.local, *.SASVIYA34, *.SASVIYA34, localhost, 127.0.0.1, 0:0:0:0:0:0:0:1, 192.168.7.89, fe80:0:0:0:ad1e:5c43:1ea2:61fd, 192.168.122.1]; nested exception is javax.net.ssl.SSLPeerUnverifiedException: Certificate for <SASVIYAV34.ndblab.local> doesn't match any of the subject alternative names: [SASVIYA34, SASVIYA34.ndblab.local, SASVIYA34, SASVIYA34, *.SASVIYA34.ndblab.local, *.SASVIYA34, *.SASVIYA34, localhost, 127.0.0.1, 0:0:0:0:0:0:0:1, 192.168.7.89, fe80:0:0:0:ad1e:5c43:1ea2:61fd, 192.168.122.1]
2018-11-19 16:08:15.317 INFO 14786 --- [n Asynchronous5] c.s.c.bootstrap.ConfigurationLoader : service [1b5699768634e98d] [CONFIGURATION_BOOTSTRAP_OBTAINED_ACCESS_TOKEN] An access token has been obtained.
Hello @S_S,
I have a few questions and a few suggestions:
- is this a single server install?
- are you using the linux default SSL certificate, or did you created one for the web server ?
In addition:
Ensure your short and FQDN are OK:
hostnamectl set-hostname short-name
hostnamectl set-hostname fullyquallified-name --static
update your /etc/hosts file to contain the line with actuals of (the order is important):
#<<IP ADDRESS>> <<FULLY.QUALLIFIED.DOMAIN.NAME>> <<SHORTNAME>>
Then, remove installation,
If you have one server deploymenr: edit your playbooks inventory.ini should contain a line like:
#deployTarget ansible_host=fully.quallified.domain.name
#and I would comment the localhost line out (#)
Then re-deploy.
Have you noticed that your hostname doesn’t match what’s in the certificate? i.e. sasviyaV34 vs sasviya34 The hostname has an extra V.
Hi Paul,
Thank you very much.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
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.