Reputation: 1887
If I am building a library in .NET based on, say FB or Google API, we get an access token (short lived) and a refresh token (long lived).
As a developer who wishes to build such a library, whose responsibility is it to store those tokens?
The client library developer or
The application consuming my library
Upvotes: 2
Views: 404
Reputation: 4019
I would assume the application consuming your library, since the client library doesn't know how the application wants to store the tokens. I've had tokens stored in databases. I've had them retrievable only by web service. I even had some hardcoded for a test application I worked on.
Upvotes: 2