ManiaConnect: unified authentication system

[konte]

Am I right with the assumption that the authentication status is saved with the standard PHP session function, so, with a cookie called "PHPSESSID"? If so, that's not a good name for a cookie^^ I would like to see a ManiaConnect-related cookie name, so that the user can use PHPSESSID himself.

And, if I once have confirmed that I accept to send my data, I'm not asked later anymore, am I? (so, I still have to connect, but there's no confirmation). How about two buttons, one for a permanent login, one for a one-time one?

[fastforza]

How does one go about using ManiaConnect in Manialinks? I assume it works the same. However, for the redirection URI, do we specify the Manialink name or a URI to that Manialink?

[gouxim]

Am I right with the assumption that the authentication status is saved with the standard PHP session function, so, with a cookie called "PHPSESSID"?

The authentication status is indeed saved by default in the PHP session. However you're not right about the name of the cookies. It all happens here: http://code.google.com/p/maniaplanet-ws ... ion.php#34

If the session is not already started, it starts it using session_start(); But you can obivously call session_name() (http://php.net/manual/en/function.session-name.php) before to change the PHP session cookie name. That's what we do in ManiaLib for example.

[gouxim]

How does one go about using ManiaConnect in Manialinks? I assume it works the same. However, for the redirection URI, do we specify the Manialink name or a URI to that Manialink?

It is indeed exactly the same, so you need to use the URI and not the short manialink.

[fastforza]

Thought so. Thanks for the clarification.

[tatar]

Hi,
Is it possible to implement a "remember my credentials" with the ManiaConnect?

I use it to authenticate players and they ask for this feature. I don't know where to begin I don't quite get how the ManiaConnect works.
Thanks.