Eclipse Community Forums: Oomph » password validation

Help

Home

Home » Eclipse Projects » Oomph » password validation

Show: Today's Messages :: Show Polls :: Message Navigator

password validation [message #1631130]

Mon, 23 February 2015 16:04

Bryan Hunt

Messages: 366
Registered: July 2009

Senior Member

Are there any docs on how to do password validation? I tried adapting the one I found that validates against eclipse.org to use our Jenkins server and failed.

Also, is the password validation mechanism pluggable? I'd like to create a mechanism that validates against LDAP. I'd create a Bugzilla patch for this if desired.

Report message to a moderator

Re: password validation [message #1631237 is a reply to message #1631130]

Mon, 23 February 2015 17:21

Eike Stepper

Messages: 6692
Registered: July 2009

Senior Member

Hi Bryan,

Ed has developed the entire password validation mechanism. I've cc'ed him in the hope that he can answer your question.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 23.02.2015 um 17:04 schrieb Bryan Hunt:
> Are there any docs on how to do password validation? I tried adapting the one I found that validates against
> eclipse.org to use our Jenkins server and failed.
>
> Also, is the password validation mechanism pluggable? I'd like to create a mechanism that validates against LDAP.
> I'd create a Bugzilla patch for this if desired.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: password validation [message #1632079 is a reply to message #1631130]

Tue, 24 February 2015 04:35

Ed Merks

Messages: 33258
Registered: July 2009

Senior Member

Bryan,

The one I developed is driven by annotations of the setup model, but I
only went so far as to support what was needed for the Eclipse bugzilla
and ID validations. Certainly contributions of more flexibility are
welcome.

On 23.02.2015 17:04, Bryan Hunt wrote:
> Are there any docs on how to do password validation? I tried adapting
> the one I found that validates against eclipse.org to use our Jenkins
> server and failed.
>
> Also, is the password validation mechanism pluggable? I'd like to
> create a mechanism that validates against LDAP. I'd create a Bugzilla
> patch for this if desired.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: password validation [message #1633313 is a reply to message #1632079]

Tue, 24 February 2015 20:10

Bryan Hunt

Messages: 366
Registered: July 2009

Senior Member

Hi Ed,

I started looking at the code and it seems the org.eclipse.oomph.setup.internal.core.util.Authenticator class manages authenticators through the static create() which is not extensible. Would it make sense to move the authenticator to the model as a strategy pattern? The form authenticator would then move to it's own extension much like say the myln extension.

Report message to a moderator

Re: password validation [message #1633378 is a reply to message #1633313]

Tue, 24 February 2015 21:03

Ed Merks

Messages: 33258
Registered: July 2009

Senior Member

Bryan,

I'm not sure what "moving it to the model" means but certainly one can
imagine an extension point to register something to handle the
annotations...

On 24.02.2015 21:10, Bryan Hunt wrote:
> Hi Ed,
>
> I started looking at the code and it seems the
> org.eclipse.oomph.setup.internal.core.util.Authenticator class manages
> authenticators through the static create() which is not extensible.
> Would it make sense to move the authenticator to the model as a strategy
> pattern? The form authenticator would then move to it's own extension
> much like say the myln extension.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: password validation [message #1634902 is a reply to message #1633378]

Wed, 25 February 2015 14:12

Bryan Hunt

Messages: 366
Registered: July 2009

Senior Member

Hi Ed,

Moving it to the model means just that. Model the authenticator and make it part of the setup model. I can then extend it with my own ecore. The setup code would use the instance from the setup model to verify one's credentials. The other two options would be to do it as an extension point as you said, or as an OSGi service. I'd prefer the OSGi service, but your house, your rules Smile

Report message to a moderator

Re: password validation [message #1636398 is a reply to message #1634902]

Thu, 26 February 2015 07:05

Ed Merks

Messages: 33258
Registered: July 2009

Senior Member

Bryan,

Comments below.

On 25.02.2015 15:12, Bryan Hunt wrote:
> Hi Ed,
>
> Moving it to the model means just that. Model the authenticator and
> make it part of the setup model.

That seems more "hard core" than using an annotation approach...

I can then extend it with my own
> ecore.
True, but seems far more heavy weight...
The setup code would use the instance from the setup model to
> verify one's credentials. The other two options would be to do it as an
> extension point as you said, or as an OSGi service. I'd prefer the OSGi
> service, but your house, your rules :)

We'll consider whatever you propose...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	preferences under a product
Next Topic:	Setting multi line variable value

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Dec 09 05:19:30 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter