Thanks, I have followed these instructions. The Bash script I'm executing to test comes from this page with a few changes. The problem I have is that the step that is suppose to provide a ticket does not instead returning a 404. I have found 2 references to a similar issue online, but no solution or cause of it. Since there is nothing in the logs to go by as to why it does not return a ticket other than the line: "ACTION: SERVICE_TICKET_NOT_CREATED" which does not explain why it is not created, I'm unable to continue at this time.
On Monday, May 12, 2014 1:16:53 PM UTC-4, Andrew Morgan wrote: > > On Mon, 12 May 2014, [email protected] <javascript:> wrote: > > > So it does not appear that REST is operational in my installation. > Based > > on the test above, the service could be anything and so for right now it > is > > a random URL on the same server, since I do not care. I simply wanted a > > valid ticket to be generated from the TGT. For instance I have also > tried > > using a service of * without success. > > Maybe I missed this in an earlier email, but did you enable the RESTful > API in CAS? Instructions are at: > > https://wiki.jasig.org/display/CASUM/RESTful+API > > in the Configuration section. > > Andy > > -- > You are currently subscribed to [email protected] <javascript:> as: > [email protected] <javascript:> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
