Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

[14:52:07 CDT(-0500)] <atilling> ahh then I'd do the action-state after warn, because you are changing the end-state

[14:53:04 CDT(-0500)] <foxnesn1> yes and since the checkall interrupts on occasion the user may spend up to 5 minutes on it if they are slow

[14:53:53 CDT(-0500)] <atilling> right but you're flow doesn't allow any way for them to return to the flow after checkall

[14:55:10 CDT(-0500)] <foxnesn1> yea

[14:55:28 CDT(-0500)] <foxnesn1> if you get to the checkall then it should figure you have authenticated successfuly

[14:55:40 CDT(-0500)] <atilling> yes

[14:57:04 CDT(-0500)] <atilling> that service ticket life span is another reason we built it so that the password warn and change happens inside CAS

[15:00:01 CDT(-0500)] <foxnesn> does the order of action-state matter compared to location of other action-states?

[15:04:46 CDT(-0500)] <atilling> no

[15:05:00 CDT(-0500)] <atilling> just makes it easier to read

[15:06:49 CDT(-0500)] <foxnesn> so i guess i should substitute one of these variables with my checkall action-state

[15:07:18 CDT(-0500)] <foxnesn> generateST on success goes to warn

[15:07:56 CDT(-0500)] <foxnesn> i could change that to checkall

[15:08:07 CDT(-0500)] <foxnesn> and just build it in not to have the warn feature

[15:09:33 CDT(-0500)] <foxnesn> because right now nothing transitions to my new action-state

[15:12:20 CDT(-0500)] <atilling> ok, or you could transition to warn for the states that don't go to checkall

[15:13:48 CDT(-0500)] <foxnesn> good idea

[15:16:05 CDT(-0500)] <foxnesn> hrm, met with cas is unavailable after signing in

[15:19:10 CDT(-0500)] <foxnesn> cas log shows the service ticket was created

[15:19:52 CDT(-0500)] <foxnesn> catalina shows no errors

[15:19:55 CDT(-0500)] <foxnesn> i will have to setup debug

[15:31:03 CDT(-0500)] <foxnesn> wow errors galore

[15:31:55 CDT(-0500)] <atilling> yeah but usually only the last error counts

[15:32:54 CDT(-0500)] <foxnesn> INFO: Illegal access: this web application instance has been stopped already. Could not load META-INF/services/javax.xml.parsers.DocumentBuilderFactory. The eventual following stack trace is caused by an error thrown for debugging

[15:33:00 CDT(-0500)] <foxnesn> that is the first error

[15:33:37 CDT(-0500)] <atilling> right but usually the last error is the one you need to address - that error will say caused by, which might be caused by etc

[15:33:47 CDT(-0500)] <foxnesn> which is confusing

[15:33:50 CDT(-0500)] <foxnesn> here is the last one

[15:33:52 CDT(-0500)] <foxnesn> INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.PatternLayout. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to at

[15:36:16 CDT(-0500)] <foxnesn> there must be over 100 over those same messages

[15:36:26 CDT(-0500)] <foxnesn> none SEVERE

[15:37:08 CDT(-0500)] <atilling> there will be a bunch, it can be a learning curve to understand the log

[15:37:34 CDT(-0500)] <atilling> if you use pastebin or pastie and share the log I can help you

[15:37:42 CDT(-0500)] <foxnesn> it is too large

[15:37:49 CDT(-0500)] <foxnesn> it would take hours to copy/paste it

[15:38:41 CDT(-0500)] <foxnesn> they seem to be related to XML

[15:38:51 CDT(-0500)] <foxnesn> perhaps a bug in my loginwebflow

[15:38:59 CDT(-0500)] <atilling> stop the service, delete the log files, restart, and then see what's in the log

[15:39:04 CDT(-0500)] <foxnesn> ok

[15:39:28 CDT(-0500)] <atilling> the bash script I shared yesterday has the logic to clear the log files as part of the stop/start

[15:39:47 CDT(-0500)] <kickehy> do the tomcat logs get cleaned out after a certain period of time?

[15:40:09 CDT(-0500)] <atilling> depends on your log config

[15:40:21 CDT(-0500)] <kickehy> guess i'll look then (tongue)

[15:40:28 CDT(-0500)] <foxnesn> CAS loads and i can auth against it

[15:40:40 CDT(-0500)] <foxnesn> i get the CAS not available message once i am granted the ticket

[15:41:06 CDT(-0500)] <atilling> ok so sounds like there is an error in the flow action you added

[15:41:15 CDT(-0500)] <atilling> the log should show it

[15:41:35 CDT(-0500)] <atilling> Kickehy: your cas deploy up and running now?

[15:43:14 CDT(-0500)] <foxnesn> not throwing any errors after restart

[15:43:17 CDT(-0500)] <foxnesn> this is werid

[15:43:23 CDT(-0500)] <foxnesn> same webflow samd log settings

[15:43:34 CDT(-0500)] <foxnesn> same cas unavailable mesg

[15:43:53 CDT(-0500)] <atilling> check the localhost log file

[15:44:07 CDT(-0500)] <atilling> some errors end up there instead of catalina

[15:46:52 CDT(-0500)] <foxnesn> java.lang.IllegalArgumentException: Cannot find state with id 'checkall' in flow 'login' – Known state ids are 'array<String>['ticketGrantingTicketExistsCheck', 'gatewayRequestCheck', 'hasServiceCheck', 'renewRequestCheck', 'warn', 'g

[15:47:13 CDT(-0500)] <foxnesn> postView', 'checkAll', 'moodlecheckAll', 'redirectView', 'viewServiceErrorView', 'viewServiceSsoErrorView']'

[15:48:23 CDT(-0500)] <atilling> so your transition to="checkall" but you don't have an element with id="checkall"

[15:48:54 CDT(-0500)] <foxnesn> lol

[15:48:59 CDT(-0500)] <foxnesn> i had checkAll

[15:49:01 CDT(-0500)] <foxnesn> kldfjlkfdgflkgjlgjffglkdfdkj

[15:49:40 CDT(-0500)] <atilling> yes surprise, surprise java is case-sensitive

[15:49:56 CDT(-0500)] <foxnesn> yea ha i must have missed it

[15:50:05 CDT(-0500)] <atilling> easy mistake

[15:50:39 CDT(-0500)] <foxnesn> omg it worked

[15:50:56 CDT(-0500)] <atilling> I had one once back in basic that stymed me for days, I had initialized a variable N but I was printing Z

[15:51:43 CDT(-0500)] <foxnesn> how long do tickets last?

[15:52:26 CDT(-0500)] <atilling> by default st = 2 minutes, tgt 2 hrs

[15:52:47 CDT(-0500)] <foxnesn> ok well i now the checkall works in the flow

[15:52:54 CDT(-0500)] <foxnesn> now i have to see how it handles on the other end

[15:54:11 CDT(-0500)] <foxnesn> atilling: will you be on at all tomorrow?

[15:54:58 CDT(-0500)] <atilling> I will probably be

[15:55:13 CDT(-0500)] <foxnesn> ok, im sure there will be some bugs to work out

[15:55:15 CDT(-0500)] <foxnesn> as always

[15:55:17 CDT(-0500)] <atilling> I took a half sick day today and got some extra sleep

[15:55:22 CDT(-0500)] <foxnesn> nice

[15:55:31 CDT(-0500)] <foxnesn> so it looks like the webflow is working

[15:55:39 CDT(-0500)] <foxnesn> now i need to check how that impacts PWM

[15:55:57 CDT(-0500)] <atilling> good luck

[16:04:18 CDT(-0500)] <foxnesn> hrm, after i setup my responses i get...

[16:04:19 CDT(-0500)] <foxnesn> Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

[16:04:27 CDT(-0500)] <foxnesn> and IE just hangs