In this revision:
-
A basic credentials
dialog in “org.eclipse.spaces.ui”
-
Working authProvider
extension point in “org.eclipse.spaces.core”
Which means J
:
-
It is now possible to ask
for credentials for a SpaceResource, and if it is not known by
SpaceAuthroization the new dialog will open (if the core plugin is used
in combination with the ui plugin).
-
A headless configuration
can either provide an extension to prompt the user, or get credentials from the
command line and add them to the SpaceAuthroization
-
SpaceAuthroization
supports credentials that are temporary (in memory, lost when the IDE closes),
or credentials persistent in the Eclipse keyring.
-
(And, if a user wants to,
they can use Eclipse’s capability to password protect the keyring)
Notes:
-
When requesting
credentials, it is possible to ask for various aspect of the Space; typically
the entire SPACE, the FLAT area, the STRUCTURED area, or SOURCE repo, but there
is also support for getting credentials for PROVIDER, SERVER, and USER
(i.e. wider scopes than SPACE). These more advanced scopes are not supported in
this version of the dialog – it will always store credentials for the
SPACE scope. As an example, if a request is made for the FLAT area, and
credentials were not found – the dialog pops, and user enters credentials
– these credentials are then applied to the SPACE. After this, subsequent
requests to the SPACE, FLAT, STRUCTURED, or SOURCE will get the same
credentials.
-
If wanted, it is easy to
extend the user dialog so the user can select the scope of the entered
credentials. (Don’t think we need this for EclipseCon as AOL will have
the same login/password for all three areas).
Regards
- henrik