Cluster Support: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann jgroups |
imported>Hendrik Brummermann →Tasks: Authentication |
||
| Line 23: | Line 23: | ||
=== Authentication === |
=== Authentication === |
||
When the client connects to a different cluster node, it has to authenticate it self. In order to support the inital web based login with a one time secret, the username/password cannot be used. There are two alternatives: |
|||
* The login secret can be part of MessageS2CForward, This approach has the advantage that code for the login is already there for the web based login. |
|||
* Use a sessionid that is generated on login and valid until the player logs off (or 5 minutes after he is last seen). This sessionid has to be maintained the server side and a new login message is required. On the positive side this sessionid can be used for reconnecting after the connection was lost. |
|||
=== Cross node zone change === |
=== Cross node zone change === |
||