Ennio Martinez Posted June 10, 2013 Share Posted June 10, 2013 Dear, Good afternoon! I Configured the NetScaler access gateway 10.1, and when access externally placing a domain account this error appears: Error: Not a privileged User. Already configured LDAP authentication and tested with the administrator account. regards Link to comment Share on other sites More sharing options...
Ennio Martinez Posted June 11, 2013 Author Share Posted June 11, 2013 Solved Link to comment Share on other sites More sharing options...
Ennio Martinez Posted June 11, 2013 Author Share Posted June 11, 2013 solved Link to comment Share on other sites More sharing options...
Martin Lapointe1709152027 Posted July 31, 2013 Share Posted July 31, 2013 How did you solved the issue ? I m having the same probleme and can't figure out what is happening !! Thank you Link to comment Share on other sites More sharing options...
Martin Lapointe1709152027 Posted August 2, 2013 Share Posted August 2, 2013 Solved by changing from DENY to ALLOW in the netscaler Profile setting, under security tab on Default Authorization Action Link to comment Share on other sites More sharing options...
Evan Chadwick1709156803 Posted January 10, 2017 Share Posted January 10, 2017 Not a recommended approach to set the default to Allow. Link to comment Share on other sites More sharing options...
Paul Blitz Posted January 11, 2017 Share Posted January 11, 2017 "Not a Privileged user" means that the user has connected ok, but has not been authorised to access backend resources. There are several ways to fix this: - use authorisation policies (the only safe way to do it with full VPN / Clientless VPN, but also a valid way to do it for ICA Proxy) - set the Default Auth action of a session profile to Allow (not safe for full VPN / Clientless VPN, but fine for ICA connections*) - set the global Default Authorisation to Allow (NOT SAFE!) * it is quite safe to set the Session Profile's Default Authorisation to Allow for ICA Proxy connections, as we are in full control of what the user gets connected to (Storefront, as set in the profile, and from there to any HDX = ICA connections). There's no way for the user to access anything outside of the XD setup. Link to comment Share on other sites More sharing options...
Yuri Shatalov Posted June 9, 2020 Share Posted June 9, 2020 Hello! I got the same error. I've created a authorization policy (CLIENT.TCP.DSTPORT.EQ(445)||CLIENT.TCP.DSTPORT.EQ(139)) and bind it to the AAA group. But thr same error. Link to comment Share on other sites More sharing options...
Hailey Horsley Posted February 21, 2023 Share Posted February 21, 2023 On 8/2/2013 at 9:54 AM, Martin Lapointe1709152027 said: Solved by changing from DENY to ALLOW in the netscaler Profile setting, under security tab on Default Authorization Action Been a few years, but recently ran into this same issue while upgrading from 12.1 to 13.1 - default auth action reset to "DENY" and was dropping all otherwise valid AAA attempts. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now