Difference between revisions of "SLGOGP Draft 1/Discuss 3-1 Login"
Jump to navigation
Jump to search
Gigs Taggart (talk | contribs) (conditional success) |
Gigs Taggart (talk | contribs) |
||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
What is the exchange here for an expired password that needs to be changed before logging in? I'm not sure this should be a straight failure. Is it possible to rework "select agent" to request arbitrary additional information? Making this bit extensible might be a good thing. [[User:Gigs Taggart|Gigs Taggart]] 08:36, 29 May 2008 (PDT) | What is the exchange here for an expired password that needs to be changed before logging in? I'm not sure this should be a straight failure. Is it possible to rework "select agent" to request arbitrary additional information? Making this bit extensible might be a good thing. [[User:Gigs Taggart|Gigs Taggart]] 08:36, 29 May 2008 (PDT) | ||
:wouldn't that be agent-domain specific? Seems to me that this would be a function of the client software. There's no real loss of time resubmitting a 3 word login (first, last, password), so its just a matter of how the client software handles it.[[User:Saijanai Kuhn|Saijanai]] 16:04, 29 May 2008 (PDT) | |||
:No, there's no way the client can tell why or how it "failed". There definitely needs to be a "deferred login" type function. Instead of hard coding the "agreed to TOS" into the protocol, that should use this too. [[User:Gigs Taggart|Gigs Taggart]] 23:47, 30 May 2008 (PDT) |
Latest revision as of 22:47, 30 May 2008
Conditional login success
What is the exchange here for an expired password that needs to be changed before logging in? I'm not sure this should be a straight failure. Is it possible to rework "select agent" to request arbitrary additional information? Making this bit extensible might be a good thing. Gigs Taggart 08:36, 29 May 2008 (PDT)
- wouldn't that be agent-domain specific? Seems to me that this would be a function of the client software. There's no real loss of time resubmitting a 3 word login (first, last, password), so its just a matter of how the client software handles it.Saijanai 16:04, 29 May 2008 (PDT)
- No, there's no way the client can tell why or how it "failed". There definitely needs to be a "deferred login" type function. Instead of hard coding the "agreed to TOS" into the protocol, that should use this too. Gigs Taggart 23:47, 30 May 2008 (PDT)