Sergey, >You do not have to compile it or indeed even build the whole distro; >just remove a reference to the parent pom, and add the missing version >properties, example, add cxf.version: 2.7.1, etc
Got it! Please bear with me. My interpretation of this is: Whatever library files needed by the examples will be loaded from a maven repo (?), such as cxf-rt-rs-security-oauth2-2.7.0.jar So all I need to do is download the subpackage on Oauth2 (which gives me an application to test out) https://github.com/Talend/tesb-rt-se/tree/master/examples/cxf/jaxrs-oauth2 and compile it to get a war file (all the relevant libs are done automatically by maven repo downloads). Pls confirm. >it is all about linking in IDP & OAuth2 applications in a way >which makes sense for a particular application, though of course using >the standard mechanisms Thanks again. My impression was exactly that when 'started out. >In fact: why don't use your own IDP ? Yes, that my intent. Looking for a any specifics I need to configure on shib idp. >this is why is used as a point of reference, >but the demo is supposed to work with any IDP which supports Web SSO Sweet. Will get started with the oauth2 example. Looks like you folks have done a tremendous work here. Ofcourse, 'am a newbie to cxf, so its a learning curve for me. Thanks and good day -Greg -- View this message in context: http://cxf.547215.n5.nabble.com/Oauth-2-provider-lib-and-Qs-tp5719975p5720376.html Sent from the cxf-user mailing list archive at Nabble.com.
