I've been using ServiceNow with a private BitBucket repo for a while now using app passwords with no issues. However, after upgrading ServiceNow to its latest version it's begun refusing me access to the repo using the same credentials that used to work fine, claiming the user lacks write privileges.
I'm not sure how they're poking at the repo to check for credential privileges but it clearly isn't working right. Is this a bitbucket thing or a ServiceNow thing?
If the upgrade of ServiceNow stopped something working, then yes, I'd be looking at the upgrade as the source of the problem, not the system that has not changed.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.