Authorization Process Issue

[benrwoodard]

When a user attempts to re-authenticate the OAuth token, the user receives a 401 error. The current process is to attempt a minor API call function such as get_me() and after getting the 401 error, then trying the aa_token() function again. Need to sure up the authentication process.

[benrwoodard]

I think we need to document this issue and move on. It's an adobe thing that is not allowing the refresh token to work. Documentation could be as simple as "See a 401 error? Rerun aw_token() again" What do you think? We could setup some error handling but if Adobe fixes the problem that catch may prevent our refresh from happening.

[gilliganondata]

I'm good with that. Working day to day with it and having the token expire has been _minimally_ disruptive. We probably need to leave the issue open, but we can add the documentation and know this is going to sit open just so people can find out what's going on if they run into it and can't find the documentation.

…

On Tue, Dec 1, 2020 at 4:28 PM Ben Woodard ***@***.***> wrote: I think we need to document this issue and move on. It's an adobe thing that is not allowing the refresh token to work. Documentation could be as simple as "See a 401 error? Rerun aw_token() again" What do you think? We could setup some error handling but if Adobe fixes the problem that catch may prevent our refresh from happening. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AET7RJ5RDUNSN47OYLNMR33SSVNYLANCNFSM4TKQ6MAA> .