Topics created by megeshg

Hmmm. That seems to be a bug, because the aud claim should be absent from the authorization code grant, since the user isn't registered for that application.

I filed an issue: https://github.com/FusionAuth/fusionauth-issues/issues/713

Hiya,

I'm glad you were able to make the device grant work.

I looked in the issues list and found this one: https://github.com/FusionAuth/fusionauth-issues/issues/248 which seems similar but maybe not exactly what you are looking for. If it is, please vote for it.

If it isn't, I'd encourage you to file an issue explaining exactly what you'd like, so that others can give feedback. We can't commit to timelines or implementations (unless you engage us for support or professional services) but definitely look at the number of votes for features when planning our roadmap.

At this time I'm not aware of any plans to store/display how many devices are linked to a user, which means that building it out in your codebase is probably the best path forward.

You could possibly leverage the user.data field and update it right after the grant is complete. This would give you the ability to search that in Elasticsearch.

Hope this helps.

@megeshg said in Authorize device without using /oauth2/device redirect:

we are not call /oauth/device would we need to? when in the flow would we need to do this? Dont see this in the documentation?

Hmmm. I think I must have been mistaken when I suggested that. I can't track down where I came up with that. My apologies.

I'm glad you found a solution.