in reply to LWP::Authen::OAuth2 terminology
You are the user (consumer, client).
Look at the curl example on your provider's site. It's about as basic as one can get. The constructor for LWP::Authen::OAuth2 requires the information that is needed for the request_token call, which is how you actually authenticate the client (instance of LWP::Authen::OAuth2). The instance (client) will then utilize the token when making calls via get, post, etc.
Most of the complication is actually on the provider's end in facilitating the "conversation" that generates the token and sets access controls; but this is all done on the provider's end. LWP::Authen::OAuth2 is for the one making the API calls (you).
Update - not sure, but looks like there are some service specific provider modules, e.g., LWP::Authen::OAuth2::ServiceProvider::Dwolla. So I am not sure if it's ready to roll out of the box or it just provides a foundation for something whacky a provider might do. Good luck.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: LWP::Authen::OAuth2 terminology
by cormanaz (Deacon) on Sep 04, 2020 at 16:31 UTC | |
|
Re^2: LWP::Authen::OAuth2 terminology
by cormanaz (Deacon) on Sep 03, 2020 at 14:59 UTC | |
by perlfan (Parson) on Sep 03, 2020 at 15:16 UTC |