[#KERN-591] Secure key, secret, and url properly

Nakamura

KERN-566

Secure key, secret, and url properly

Created: 04-Feb-2010 10:02 Updated: Tuesday 11:55 PM

Component/s:

Hybrid S2 - S3 Integration

Affects Version/s:

0.3

Fix Version/s:

0.4

Time Tracking:

Original Estimate:

1 day

Remaining Estimate:

1 day

Time Spent:

Not Specified

Description

« Hide

I have three properties that are currently stored on a sakai/basiclti node (i.e. ltiurl, ltikey, ltisecret) that should only be readable by the users that have permission to edit said node. The primary problem is that the GET servlet needs to be able to read these properties on behalf of every user as part of creating the OAUTH token.

1) The AccessControlManager(?) does not support per property ACLs, which means I need to create a child node to store these secret properties and ACL that node appropriately? For normal users I would then need to loginAdministrative() to read these properties to create the OAUTH token.
2) Or maybe override GET for type sling/servlet/default to removed these properties from the response?
3) Is there another approach I am missing?

All

Comments

Work Log

Change History

Subversion Commits

git Commits

Sort Order:

[ Permlink | « Hide ]

Lance Speelmon added a comment - 04-Feb-2010 10:03

From Ian Boston: #1 sounds good.

[ Permlink | « Hide ]

Ian Boston added a comment - 16-Mar-2010 23:55

Further thoughts.

JCR protected properties cant be updated by normal sessions, only internally inside Jackrabbit which prevents any update except by code specifically designed to perform that update (ie not the default sling servlet).

Creating a sub node that is only readable by an administrative session, and contains a protected property where the protected property is not auto created will mean:

only admin can read the property.
only the code that you designed to write the property can create and write the property.

It needs some more analysis, but those 2 might give you the protection required for this use case.