Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apikey Authenticator failed due to webservice token issue #38

Open
qifeng-bai opened this issue Jan 19, 2024 · 0 comments
Open

Apikey Authenticator failed due to webservice token issue #38

qifeng-bai opened this issue Jan 19, 2024 · 0 comments
Assignees
Labels

Comments

@qifeng-bai
Copy link

qifeng-bai commented Jan 19, 2024

Spatial including hub and service has to support apiKey since the external holders are relaying on it. We cannot remove the apiKey support from spatial at this moment.

after we configured webservice.jwt section in spatial-service config, When spatial-hub calls spatial-service via apiKey, it reports a 'invalid client' error from

https://github.com/AtlasOfLivingAustralia/ala-security-project/blob/43a1cc93baa3d68bacf975caf5e1ddda42d441eb/ala-ws-security/src/main/java/au/org/ala/ws/security/authenticator/AlaApiKeyAuthenticator.java#L79

The error message is :
rg.pac4j.core.exception.TechnicalException: Bad token response, error=invalid_client, description=null ... at au.org.ala.ws.tokens.TokenClient.executeTokenRequest(TokenClient.groovy:37)

However, after we removed the webservice.jwt section from spatial-service config, it works.

We can reproduce error from Spatial-hub -> Add to map -> Area -> import KML

It may be linked to this issue as well: AtlasOfLivingAustralia/spatial-hub#467

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants