Closed notesjor closed 1 month ago
Hi Jan, sorry it took a while to response. There is no new changes in the API regarding the OAuth2 authorization flow. I have just checked the authorization flow using my client and cannot reproduce the issue. Did you get any error message?
We have investigated the problem. The issue is caused by recent changes (i.e., access restriction to owner and admin only) in the client info API that is used by Kalamar in the authorization process.
@notesjor I have rolled out a quick fix on the test instance. Could you please check?
The error has not yet been fixed in the current KorAP instance. However, the “Client not found” error no longer appears. But you still don't get to the page with the accesses, you're forwarded directly to the KorAP search. This means that OAuth2 still does not work from my side (as before).
Were you using the test instance? It looks like you were testing it on the main instance. As I understood margaretha she rolled it out on the test instance.
Yes, please check on https://korap.ids-mannheim.de/instance/test. If it is fine, I will deploy it on the main instance.
Ah ok, that explains it. Thank you. I can't test it to 100% - but it seems to work.
The main instance has been updated with the hot fix.
tested - works again as expected - thanks alot 👍
The following error is critical - I ask for quick response. The function has already worked - it is already in use in several productive applications.
For some time now, the previous OAuth2 authentication has no longer worked.
The following used to work:
Now:
Therefore: Something in the routing seems to be wrong.