authenticator solution used for web services also

[Harjo]

Hi,

we have an authenticator solution, which has a bunch of methods to create new tenants/customers, etc...
The methods can be called, from our login solution, so far so good.

Now we want to give potential customers the opportunity to do this from our website, so we want to use the servoy webservice plugin for that.
Is it recommended, or are there issues, that we use the authenticator solution directly ALSO as a webservice solution?

Because, we don't want to duplicate all the functionality, into yet another solution, which does practically the same....

[jcompagner]

let me understand this correctly
you have an authenticator solution that creates stuff?
That looks like admin stuff to me that doesn't belong in an authenticator solution (that is just for giving you some data)

[lwjwillemsen]

Johan,

That looks like admin stuff to me that doesn't belong in an authenticator solution (that is just for giving you some data)

Authenticator => enhanced security => very good place to check and eventually write security / license related data !

Regards,

[Harjo]

Indeed, potential customers will open the login solution first, they dont have have credentials yet, in the login solution there is button, register now!
they fill up a couple of fields, and all those values are send to the authenticator solution and checked server-side if the companyname does not exist, if the email is valid, etc....
if everything is correct, the autenticator solution, creates the account for you, and the potential customer gets an email with the credentials..

pretty common stuff... We had this already in Servoy 2, but now with the enhanced security, we HAVE to do it now with the authenticator solution.
it works like a charm, so that is not the question.

the question is, if I can use the authenticator solution, ALSO as a webservice?

[rgansevles]

Harjo,

You can't use an authenticator solution directly as a web service.
These are 2 quite different things.

Best to put all your authentication logic in a module that is shared between your authenticator solutions and your webservice solutions.
You can use an authenticator solution as a module directly in your webservice solution if you want to.

Rob

[Harjo]

Thanks for the explanation Rob, I understand now!

[jcompagner]

Indeed, potential customers will open the login solution first, they dont have have credentials yet, in the login solution there is button, register now!
they fill up a couple of fields, and all those values are send to the authenticator solution and checked server-side if the companyname does not exist, if the email is valid, etc....
if everything is correct, the autenticator solution, creates the account for you, and the potential customer gets an email with the credentials..

So i still would divide it up this is why we have modules

you have a module "admin" and a module "authenticator"

the authenticator does really nothing more then authenticating users, The admin module (thats still can be a module of the "authenticator" is really for admin stuff)

Then if done this way it is still modular and you can reuse the admin pages just fine without having to drag on the authenticator stuff.

[Harjo]

I will create an admin module and put there the tenants creation method,
that module, is than a module of the authenticator, and that module is module of our webservice solution.