Perl 6 - the future is here, just unevenly distributed

IRC log for #openam, 2013-12-01

| Channels | #openam index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:14 aldaris joined #openam
00:32 aldaris joined #openam
01:01 aldaris joined #openam
02:12 aldaris joined #openam
03:46 aldaris joined #openam
04:21 aldaris joined #openam
08:38 jjpp joined #openam
09:56 jjpp_ joined #openam
10:49 jjpp joined #openam
11:23 ludovicp joined #openam
12:37 jjpp_ joined #openam
13:14 ludovicp joined #openam
13:29 aldaris joined #openam
13:30 MegaMatt joined #openam
15:06 jjpp joined #openam
16:07 aldaris joined #openam
16:21 aldaris joined #openam
16:37 aldaris joined #openam
17:02 ludovicp joined #openam
17:25 aldaris joined #openam
18:10 aldaris joined #openam
19:06 aldaris joined #openam
20:57 MegaMatt joined #openam
22:06 aldaris joined #openam
22:32 aldaris joined #openam
22:58 aldaris joined #openam
23:21 balo i have a question and it's quiet here, so: i have a custom ldap auth module with a custom user lockout functionality and I return own int state from the process method and based on this i can show a custom lockout screen (it solved with a length=1 callback and a custom template). Could I somehow communicate it to the applications protected with agents? I mean a custom redirect, maybe with my custom replaced header, so an app can show
23:39 aldaris not sure I follow, what do you mean?
23:42 balo the requirement is that the application should display the user lockout error with the message when the lockout will expire (message assembled and expire time calculated by the auth module).
23:43 aldaris good luck with that then
23:43 aldaris why isn't the app doing that from the beginning?
23:43 aldaris maybe the new REST auth interface in 11 can be used for this, but I doubt you are using 11 already :p
23:44 balo yeah, the migration to 11 planned to april 2014. I mean the beginning of the project... :D
23:45 balo this perhaps will be needed in january.
23:45 aldaris right, then maybe using the clientsdk, but it really depends on how the module implements it I guess
23:50 balo the basic problem is the application should know why the login failed. The user gave wrong credentials or she locked out.
23:52 balo if the app knows about the locking, maybe i can say that they should query the data from the ldap and calculate it. It could cause a maintenance issue if the lockout expire calculation changes. I could live with that.
23:55 aldaris usually errors are badly returned to clients from auth modules, so I'm not sure how to go about this really, I'd say error states in the callbackdescriptors, and parse those. Of course the app would then use the clientsdk to authenticate
23:57 balo thanks, i'll look into it
23:59 balo anyway, i understand why it's not that simple... if somebody have more auth modules in a chain, and the optional modules can leave different error states. It sounds complicated to do it generally.

| Channels | #openam index | Today | | Search | Google Search | Plain-Text | summary