support Posted August 18, 2017 Posted August 18, 2017 When trying to access the new Windows API Documentation from the Help menu in Passwordstate 8, it is possible you get a Windows based prompt asking for a username and password. To fix this, please ensure your Passwordstate URL is located in the Local Intranet Zone. To see if it is located in the Local Intranet zone, open Internet Explorer, browse to your website and open Internet Options -> Security. If it is detected it is in the Local Intranet zone, it will appear blue as per below screenshot: If you need to you can add the site in the Internet Options above, or add the site to group policy to ensure all machines detect it by default.
briank Posted August 18, 2017 Posted August 18, 2017 I am still getting prompted for username and password and it will not be accepted. The "Windows Integrated API Documentation" is the only page with this behavior thus far. You do not have permission to view this directory or page.
support Posted August 19, 2017 Author Posted August 19, 2017 Hi Brian, Is your URL being detected in the Local Intranet Zone in IE - can you share a screenshot? And can you tell us which browser you are using? If it is, then the following forum post provides a few more suggestions which will fix this - https://www.clickstudios.com.au/community/index.php?/topic/1305-passwordstate-prompts-for-authentication/ Can you let us know if any of the following helps? Regards Click Studios
briank Posted August 19, 2017 Posted August 19, 2017 We are able to get to the documentation simply by adding winapi to the end of the url replacing api instead of using the link provided on the page. https://server:9119/api/ https://server:9119/winapi/
support Posted August 19, 2017 Author Posted August 19, 2017 Hi Brian, Those two buttons below should take you to each of the relevant URLs - are they taking you to a different URL?
briank Posted August 21, 2017 Posted August 21, 2017 I am able to get to the documentation from the above links now. I am not sure if a setting was changed (I am not the only one working on this) or if by accessing it by directly going to the winapi page has somehow "repaired" the link.
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