What do we, as a team, want to do about specialized features? OpenID support is a good thing to have, but is probably not the majority use case. How should we handle multiple implementations within Rave? Is it possible with maven to choose a set of implementations at build time via profiles?
-Matt On 5/6/11 4:37 PM, "Raminderjeet Singh (JIRA)" <[email protected]> wrote: > > [ >https://issues.apache.org/jira/browse/RAVE-23?page=com.atlassian.jira.plug >in.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030127#commen >t-13030127 ] > >Raminderjeet Singh commented on RAVE-23: >---------------------------------------- > >Added openid support. Currently you need to use >http://rave2011.myopenid.com/ as that is the only registered id in >initial_data.sql and for login to myopenid use rave2011. You can add more >URLs into the script. Registration of new openid should be handled in >user registration. We need to find how can we associate existing user >with openid URL. I used default view page for openid. > >> Implement OpenID authentication >> -------------------------------- >> >> Key: RAVE-23 >> URL: https://issues.apache.org/jira/browse/RAVE-23 >> Project: Rave >> Issue Type: Sub-task >> Reporter: Marlon Pierce >> Assignee: Raminderjeet Singh >> > > >-- >This message is automatically generated by JIRA. >For more information on JIRA, see: http://www.atlassian.com/software/jira
