On Thu, Aug 14, 2008 at 11:52 PM, dale77 <[EMAIL PROTECTED]> wrote: > > 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.
The wiki is stating the general case. The final configuration completely depends on how you configure it in web.xml. If you mapped it to /scott/* then the wiki would be wrong too because it would be /scott/tickets :-) > > 2. The location response from from a POST to /cas/v1/tickets looks like > this: > > https://www.whatever.com/cas/v1/{TGT<https://www.whatever.com/cas/v1/%7BTGT>id} > > However the wiki states it should be > > https://www.whatever.com/cas/tickets/{TGT<https://www.whatever.com/cas/tickets/%7BTGT>id} I'll have to look into that. It should be /cas/v1/tickets/{TGTID} (where "v1" is the versioning prefix, and /cas is the context you've deployed CAS in) I won't be able to check it until later though. > > 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). The problem is the protocol is correct and so is adding "v1" ;-) Anything before /tickets is up to you to define. Even /cas is optional if you've deployed as a ROOT context. Depending on where you've deployed CAS a correct mapping could be /v1/tickets So /tickets is correct. Anything before that is up to you. -Scott > > 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 >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
