[security-dev] PicketLink SCIM Module
Anil.Saldhana at redhat.com
Wed May 22 09:33:57 EDT 2013
On 05/22/2013 06:54 AM, Anil Saldhana wrote:
> On May 22, 2013, at 6:34 AM, Shane Bryzak <sbryzak at redhat.com
> <mailto:sbryzak at redhat.com>> wrote:
>> I've spent some time today reviewing the RESTEasy reference docs 
>> and source code . Its primary security focus seems to be on OAuth
>> and request-signing, which I'm happy to steer clear of for the time
>> and DIGEST authentication client. I think we still need to start a
>> separate discussion in conjunction with Bill for the OAuth topic and
>> where PicketLink fits into this, perhaps next week sometime we could
>> even have a call or hangout to work out our next steps.
>> Back on topic for PicketLink though, would it be ok Anil if we went
>> ahead and renamed the SCIM module to REST, and began prototyping the
> Cool. I think we should aim scim beyond the 2.5 release.
Also while we are on the REST security topic, I think we will need a
JAX-RS interceptor to introduce security into the apps. But the
interceptor is standardized in JAX-RS 2.0 (EE7). For EE6 apps, I think
we will have to use RESTEasy interceptor (which means a deep coupling).
>>  https://github.com/resteasy/Resteasy/tree/master/jaxrs/security
>> On 21/05/13 23:27, Anil Saldhana wrote:
>>> Rest module can have scim as well as oauth base. We need to ensure that we do not conflict with RESTEasy as it has many security features.
>>> On May 21, 2013, at 7:56 AM, Pedro Igor Silva<psilva at redhat.com> wrote:
>>>> But regarding the two set of RESTful services, maybe we can have only a SCIM set where the PicketLink additional features can be handled as extensions to the base schema.
>>>> ----- Original Message -----
>>>> From: "Shane Bryzak"<sbryzak at redhat.com>
>>>> To: "security-dev >> \"security-dev at lists.jboss.org\""<security-dev at lists.jboss.org>
>>>> Sent: Tuesday, May 21, 2013 5:22:06 AM
>>>> Subject: [security-dev] PicketLink SCIM Module
>>>> I've been reviewing the capabilities of the SCIM module (which are defined by the SCIM specification ) and someone correct me if I'm wrong, but it only seems to provide a subset of the features that we support in PicketLink. Specifically missing are authentication, and support for the extended relationship types (basically everything besides group membership). I'm wondering if it might be worth providing a PicketLink REST module instead, which would provide two sets of RESTful services; the first being a SCIM-compliant service, the second being a more proprietary service that exposes all of the capabilities of PicketLink.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the security-dev