Community
Participate
Working Groups
When a ConnectorService uses the StandardCredentialProvider, and connect() is called with forcePrompt==false, there is no need to pop up a UI in case a password has been stored. In this case, the StandardCredentialProvider should work completely without ANY UI requirements, in order to make it possible to work in headless applications. I believe that this can be achieved by defining the StandardCredentialProvider in a non-UI plugin, defining an ICredentialPrompter interface in non-UI as well, and implementing StandardCredentialPrompter in UI. The StandardCredentialProvider should delegate to the prompter and instanciate it ONLY if either * forcePrompt==true, or * a password has not been saved, or * an error occurs with the saved password. If the StandardCredentialPrompter instance has not yet been created by the UI, it is OK to return an error (i.e. headless applications are unable to log in if no password has been saved and no prompter has been set). applications should be able to set the prompter in the credential provider, or in the connector service.
The StandardCredentialsProvider is a prompting provider. If an alternative mechanism is needed it can be done by subclassing AuthenticatingCredentialsProvider for now. Deferring to future and leaving as an enhancement.
Moving enhancements to the 3.1 release.
