Extension upgrade fails to use new bearer token #12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After upgrading the extension the change of the bearer token fails and thus can't connect to the scim endpoint.
Are sure that on both sides, the same token and auth mode are saved ?
I just had an similar issue, that i changed the url of the scim endpoint and it wasn't saved. Not sure why this is happening. In both cases i had to recreate the scim user federation to fix it.
In the second case i saw that url was still the old one, even though the ui showed the new one.
I see. There is some cache/concurrency issue with the federation model, and it stores multiple values for the same field. And then it becomes not very deterministic... I did a dump lock mechanism : when scim is working it disables the federation provider to avoid loops with events and re-enables it when finished.
I'll some time to implement this in a better way.
Okay, I pushed a fix. It'll not fix the multiple values in the db, the easier way is to recreate the federation provider. Tell me if you see this behavior again.