User Authentication

[Jeff]

If I wanted to pass more than just username and password from an SGS client to an SGS server during authentication, for example to include an Integer representing site_id, what would I need to do? 

To  do fancier things you would:

(a) Override the authenticator with your own authenticator
(b) Create your own sub class of identity
(c) Create a custom service to read that sub class and return information from it.

All this is explained more in the extension manual.  AMMTB it will be out with the GPLd release.

[jeff_seattle]

Currently, SGS client can only request authentication using <username> and <password>, and its authentication responce is a boolean responce of either loggedIn or loginFail.

I want to expand the authentication functionality.

From my understanding, the following flow graph is a crude representation of a SGS login authentication… 

SGS client...Requesting Authentication
            SimpleClient::login()

            implemented PasswordAuthentication SimpleClientListener::getPasswordAuthentication()
                        with responce of java.net.PasswordAuthentication with credentials data <username, password>

SGS server...Processing Authentication
            implemented Identity IdentityAuthenticator::authenticateIdentity( IdentityCredentials )
                        with request of com.sun.sgs.auth.IdentityCredentials id,
                                                which is implemented NamePasswordCredentials with credentials data <username, password>
                        with response from this method is com.sun.sgs.auth.Identity,
                                                which is implemented com.sun.sgs.impl.auth.IdentityImpl with <username>                     

SGS client...Getting Authentication
           implemented boolean SimpleClientListener::loggedIn()
OR
           implemented SimpleClientListener::loginFailed(String reason)

+++++++++++++++++++++++++++++++++++++

What I want to do is the following... 

SGS client...Authentication request
            SimpleClient::login()

            implemented IdentityCredentials SimpleClientListener::getIdentityCredentials()
                        with responce of implemented CustomIdentityCredentialsImpl with credentials data <x, y, z, ...>

SGS server...Processing Authentication
            implemented Identity IdentityAuthenticator::authenticateIdentity( IdentityCredentials )
                        with request of com.sun.sgs.auth.IdentityCredentials id,
                                                which is implemented CustomIdentityCredentialsImpl with credentials data <x, y, z, ...>
                        with response from this method is com.sun.sgs.auth.Identity,
                                                which is implemented CustomIdentityImpl with data <a, b, c, ...>                     

SGS client...Authentication response
           implemented boolean SimpleClientListener::loggedIn(com.sun.sgs.auth.Identity)
                                                which is Identity instance of CustomIdentityImpl with data <a, b, c, ...>                     
OR
           implemented SimpleClientListener::loginFailed(String reason)

Thanks

[Jeff]

In about 4 weeks the stack extension manual will be out and all we be clear grasshopper.

Sorry, but I am writing the manual for a reason.  All that you want to do is doable, but I really don't have the bandwidth to be re-writing the manual in forum posts.  Wait til it comes out.  read it, and then fire any remaining questions at me.

Games published by our own members! Check 'em out!

[Middy]

Whats the rendezvous for the manual?

[galthaus]

I believe Jeff has said that the documents are set to be released to coincide with the release of the SDK soon after the Java One conference.  I think that is next week.

[Jeff]

Yes, thats correct.  The manual will go out with the open source release.  Unitl that time some of thsi is in enough flux that we don't want to mislead you.

I don't have a clear ETA  on the open source release yet except that we won't make JavaOne as we had originally hoped.  I apologize profusely for that but the team wants to make sure what they drop on you is really reasonably complete.

Til then, for design considerations:

There are basically two issues here , though you can eliminate one of them with a pit of pain.

The first issue is that you need to write a custom authenticator.  thats actually not so hard.  if you want a  peek at how to do that ahead of time, there is a good thread I've referenced in the FAQ plus BunnyHunters which *will* be released for JavaOne contains an actual example.

The second is the issue of getting your multiple parameters up to the authenticator.  You have two chocies here
1) The more work, technically proper solution.  Implement a custom protocol and your own client side API extension around it.

2) The sneeky quick and dirty method:  pack them all into a char array and use the existing API and protocol

[MickeyB]

is the "out of the box" api for base level username/pass authentication out or coming with your stuff after JavaOne?   Just want to mimic what kevglass did in tank, which is what I do now in CubeWars (sgs2).

[Jeff]

is the "out of the box" api for base level username/pass authentication out or coming with your stuff after JavaOne?   Just want to mimic what kevglass did in tank, which is what I do now in CubeWars (sgs2).

Base hashed password support is in the SDK.  You need to enable it though.

See the thread mentioned.