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.

Sign up for GitHub

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

Jump to bottom

Expired API key stops a UI user from running searches #157

Open
stroomdev10 opened this issue Oct 7, 2019 · 3 comments
Open

Expired API key stops a UI user from running searches #157

stroomdev10 opened this issue Oct 7, 2019 · 3 comments
Labels
bug
Projects
stroom-auth

Comments

@stroomdev10
Copy link
Member

It appears a UI user cannot query if they have an expired API key.

FetchDataSourceFieldsAction is where it appears to throw the first WARN (from the logs)
@stroomdev10 stroomdev10 added the bug label Oct 7, 2019
@at055612
Copy link
Member

at055612 commented Oct 7, 2019

The code that auto creates the token is stroom.security.impl.AuthenticationServiceClients#getUsersApiToken.

@jc064522 jc064522 added this to Todo in stroom-auth Oct 25, 2019
@jc064522 jc064522 moved this from Incoming to Doing in stroom-auth Nov 4, 2019
@jc064522 jc064522 moved this from Doing to Done in stroom-auth Nov 5, 2019
@jc064522 jc064522 closed this as completed Nov 5, 2019
@jc064522
Copy link
Member

jc064522 commented Nov 5, 2019

Expired API keys are now automatically re-created so queries don't fail.

@stroomdev10
Copy link
Member Author

stroomdev10 commented Nov 11, 2019 •
edited

This doesn't seem like the right fix for the problem.

Why do the expired API keys get recreated? Surely the UI token has a separate lifecycle from the API key?

@stroomdev10 stroomdev10 reopened this Nov 11, 2019
stroom-auth automation moved this from Done to Incoming Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
stroom-auth
  
Incoming
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jc064522 @at055612 @stroomdev10