Ok, the RESTful API seems to be working fine with /v1/* in web.xml with the following caveats:
1. I need to POST to /cas/v1/tickets to utilize the API, the wiki states /cas/tickets, I presume this should be updated to /cas/v1/tickets to match the suggested configuration. 2. The location response from from a POST to /cas/v1/tickets looks like this: https://www.whatever.com/cas/v1/{TGT id} However the wiki states it should be https://www.whatever.com/cas/tickets/{TGT id} Generally I've been the victim of a lot of confusion as to what the "tickets" part of the RESTful API is. The protocol says: /cas/tickets, which looks a lot like a url mapping, but the suggested url mapping is actually /cas/v1 (and you must add the RESTful object identifier "tickets" after that). Do you think the protocol part of the wiki needs correcting, or do I (still!) misunderstand? Thanks Dale scott_battaglia wrote: > > By default we assume you're versioning the RESTful protocol, hence the /v1 > in front. If you're not interested in doing that you probably could > switch > the servlet mapping to /tickets/ and the routing to > /${ticketGrantingTicket} > > I haven't tried it though. > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > -- View this message in context: http://www.nabble.com/How-do-I-activate-the-new-RESTful-api--tp18885690p18993394.html Sent from the CAS Users mailing list archive at Nabble.com. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
