Q: User's access to resources via daemon using OpenID OpenID, built on-top of OAuth 2.0, provides various mechanisms for authenticating an user/application alongside authorization to specified resources.
Generally, OAuth 2.0 aids in giving third parties the ability to request access to a user's data within your system but does also provide a standard username/password authentication method.
For a daemon or "offline" style application written by a user, what would be the appropriate authentication flow?
The application will also be using roles to determine the user's level of access to a group's resources.

A: If the application is written by a user and the user trusts the environment in which that application runs, one could use the Resource Owner Password Credentials flow to achieve what you want.
