Azure Devops Repository Password Issue

[Manish Gupta]

Hi team,

I have configured Azure Devops Repository for git integration in my ontologies .

Earlier this integration was working fine. 

However the token with which it was configured was expired .
After I update the expired token in git configuration, I do see an entry in server log as below.

'Storing value for (myldapmail) @ <https://dev.azure.com/xyz-test/Test/_git/reponame> (urn:x-evn-master:product_config) '

After this when I try to push my asset into repo, I get error as 'Not Authorized' .

I have given this token full access for code to ensure Read/write access.

Is there any lag between update of password in admin section and adoption by system?
Or Is there a different process to update password .

[Richard Cyganiak]

Hi Manish,

I believe there's a bugfix in the next release to address this problem – updated git credentials do not get applied automatically.

For now, the workaround is to do a workspace refresh (an admin operation), or restart the application.

If you're on SaaS, send a message to TQ Support asking for a workspace refresh to update stale git credentials.

If you're self-hosted, have an administrator user do a workspace refresh on the Server Administration screen.

Hope that helps,

Richard