[security-dev] Merged in Social code into PL workspace
pmuir at redhat.com
Thu Oct 25 10:29:51 EDT 2012
On 25 Oct 2012, at 02:08, Shane Bryzak wrote:
> On 10/25/2012 03:52 AM, Anil Saldhana wrote:
>> recently I merged in the social login code under "social". This is
>> plain vanilla code for login using facebook and google. I need to move
>> some code for twitter login.
> Does this include the commit history? After the debacle with the IDM
> merge, Pete gave me some advice on how to merge code from another
> repository while retaining the history.
1) Get the final directory structure sorted out in the old repo (e.g. if you need it in a subdir in the new repo, do that here - IOW the root of the old repo needs to look like you want the merged in stuff to look like in the new repo
2) Add the old repo as a remote to the new repo
3) Do a normal merge.
>> Next we are going to move the federation code under "federation". This
>> will provide the SAML object model/parsing/writing.
> No problem, although it might take some time until we can look at
> integrating this with the authentication API in PicketLink core. I
> think the next step after finishing the IDM implementation should
> probably be to get the social module integrated, although that's just my
> opinion based on what I think most developers would more likely use.
>> Since I have OAuth2 implementation, I am wondering whether I should just
>> merge into social or keep a separate module called "oauth". I am leaning
>> toward the latter.
> I'm ok with either option really. The term "social" is becoming a
> little overloaded I think, so I have no problem putting OAuth into its
> own module.
> Unfortunately I couldn't make it to last week's RWP hangout so I missed
> Antoine's presentation on Agorava. Are we planning on any joint effort
> and/or integration with Agorava code?
>> security-dev mailing list
>> security-dev at lists.jboss.org
> security-dev mailing list
> security-dev at lists.jboss.org
More information about the security-dev