[JBoss JIRA] Created: (GTNPORTAL-314) Fixing oAuth in gadgets
by jerem j (JIRA)
Fixing oAuth in gadgets
-----------------------
Key: GTNPORTAL-314
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-314
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta02
Reporter: jerem j
Fix For: 3.0.0-Beta03
Right now in the gadgets, it is not possible to use backend that use an oAuth authentication.
We need to implement the oAuth Store to store the tokens into the JCR and not in memory as it is done in the default implementation (BasicOAuthStore.java)
http://fisheye6.atlassian.com/browse/shindig/trunk/java/gadgets/src/main/...
the default implementation :
http://fisheye6.atlassian.com/browse/shindig/trunk/java/gadgets/src/main/...
In this class there is 2 different things to store :
* Consumer key and secret
getConsumerKeyAndSecret()
Right now in the default implementation it is stored in a file oauth.json. This is information a user or an admin can set. I think, only admins have to set this key, so we can keep the storage in the oauth.json. If we find later that we need to often set new keys, it might be a good idea to create a specific UI for this and store it in the JCR.
If stored in the JCR, it has to be indexed by :
gadget and server
* Tokens
getTokenInfo()
setTokenInfo()
removeToken()
The default implementation store them in memory, so everytime the object is recreated, we loose the information, and so the user has to authenticate again.
We should store the information of TokenInfo into the JCR indexed by owner, viewer, gadget, server.
Be careful tokens have an expiration date, so when getting a token, we should make sure it did not expire.
To test if the implementation is working, you can try with any jira gadget that require authentication such as the watch gadget. This jira server has been configured to work with the dev version of gatein 1.0b2 :
http://jira4j.exoplatform.org/secure/Dashboard.jspa
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-474) Problem with IDM when same database is used for "portal" and "sample-portal"
by Marek Posolda (JIRA)
Problem with IDM when same database is used for "portal" and "sample-portal"
----------------------------------------------------------------------------
Key: GTNPORTAL-474
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-474
Project: GateIn Portal
Issue Type: Bug
Environment: Ubuntu linux,
Sun JDK 1.6
GateIn from trunk (revision 1166) deployed on EAP 5.0.0.GA
Reporter: Marek Posolda
Fix For: 3.0.0-CR01
When same database is used for both portal containers "portal" and "sample-portal" in database-configuration.xml, then you can see error in server log during GateIn startup (or more precisely during startup of PicketLinkIDMOrganizationServiceImpl for Portal container "portal".) Because IDM transaction is not commited, users are not created for realm "portal" and then it's not possible to login to GateIn.
By default each container has different database because database-confiuration.xml looks like this:
<property name="driverClassName" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb${container.name.suffix}"/>
<property name="username" value="sa"/>
<property name="password" value=""/>
Problem occurs when same DB is used for both containers, so URL looks like this:
<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb_shared"/>
Exception from server log is in attachement (idm-exception.txt).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months