oauth and configuration schemas

I am not sure what to do in configuration schema for new adaptors which support oauth.

These new adaptors accept a user name and password, with which they'll login internally and generate an oauth token.

Or, if you get an oauth token from lightning, they should also be able to work with oauth_token on the config object.

I am not sure what the best practice is for Lightning.

• If using oauth, user name and password are not required
• if using a username and password, oauth is not required
• Indeed, the oauth access token should probably not be exposed to the lightning UI at all?

Salesforce has two config schemas, a normal one and oauth-configuration-schema. Does lightning use the oauth one? I can't see any reference to it in the source

Start by tracing the Salesforce oauth-configuration-schema and normal configuration schema through the source, then identify how Lightning consumes adaptor configuration schemas. Review the username/password and oauth_token cases, including UI exposure, and document or implement an agreed schema behavior with maintainer confirmation.