Hi,
We have configured PAW for SSO using the PAW server full name which works well. Users can login fine using windows authentication.
However, our client says the business won't be using domain names with server names in them so they have created a FQDN/ Host name for the PAW server. When using this new workspace address users can no longer log in to workspace due to a "Authentication error". This error is the same for both windows authentication and native authentication. The error logs indicate that there is a Kerberos failure
"TM1.SSPISecurity Server is configured to only accept Kerberos package but the client is using NTLM when attempting to Authenticate".
This error message is true of when logging in via windows authentication or native authentication.
The TM1 config is set to Kerberos and the client is using Kerberos.
Both full PAW server name and the new FQDN/ Host names are registered with local intranet policy.
Are there Workspace parameters that I have need to change. PAW.ps1 has be changed to have $env:ServerName= new FQDN/ Host name
does the server name need
https://? i.e. $env:ServerName="https://hostname.domain.com" or $env:ServerName="hostname.domain.com"
Thanks,
Regards,
Paul
------------------------------
Paul Brann
------------------------------
#PlanningAnalyticswithWatson