-
Notifications
You must be signed in to change notification settings - Fork 7
Cannot get rowdy to return refresh token #64
Comments
docker-compose.override.yml
|
Update: so far, I've tracked the problem down to
|
The answer is obvious now! The refresh_token is expected to be part of token::Configuration not the top-level Configuration, yet test/fixtures/config_noop.json has it at the top level. I was so focused on the assumption that the config file was valid that I never thought to check that until now. Maybe that's a holdover from before a refactor? In any case, that might suggest that it's a good idea to validate for unexpected config keys as well as expected ones. It also suggests that maybe there are some additional tests that would be useful to catch this kind of thing, i.e. an end-to-end test of the cli server. I had to change a few other things in the config: A256 -> A256GCM, and adding an extra number to the key vector to make 32 numbers. |
Thanks for the suggestion. The JSON deserializer ignores unexpected keys. I'll look into improving the documentation and see if I can configure the deserializer to error on unexpected keys. |
If I run the docker example, and submit a request with offline_token=true, it doesn't return a refresh token in the response. Same thing if I configure the csv fixture for refresh tokens.
The text was updated successfully, but these errors were encountered: