Login Request: Difference between revisions

From Club Penguin Protocol
Jump to navigation Jump to search
imported>Jamie
No edit summary
 
imported>Refractor
1 revision: importing preprocessed wiki pages
(No difference)

Revision as of 23:55, 15 December 2013

Before the client can communicate with a zone, it must first authenticate. SmartFoxServer provides a custom login feature, which most people (who use SmartFoxServer) utilise in order to provide an additional layer of security. A login extension accepts two parameters, as documented below, and (can) return either an XML login notice (logOK), an XML login fail (logKO), or a custom event (i.e. with Club Penguin a standard Login Response.

<msg t='sys'><body action='login' r='0'><login z='w1'><nick><![CDATA[Jamie]]></nick><pword><![CDATA[d9129e4a7dbcb0bd7ae8ee6b512d92bc]]></pword></login></body></msg>

Action login
XML Node <login />
z The zone for the server to log into (w1)
<nick /> The client's requested nickname (usually wrapped with <![CDATA[ ]]> tags)
<pword /> The password (hash) the client uses to log in. This is only used with custom logins.


Club Penguin Specific

Because at this point the Club Penguin login extension code handles this request, we receive a standard Login Response.