bmdhaker / share-extras

Automatically exported from code.google.com/p/share-extras
0 stars 0 forks source link

Request token fail yammer, twitter, linkedin #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Download and move Share OAuth add-on JAR for Alfresco 4.0 to 
/var/lib/tomcat6/shared/lib
2.Download and move yammer, twitter and linkedin dashlet to 
/var/lib/tomcat6/shared/lib
3.Restart tomcat6

What is the expected output? What do you see instead?
Dashlet in dashbord, but autorisation not possible. Message: request token fail

What version of the add-on are you using? Please provide version of the
downloaded package, or Subversion revision number.
share-oauth-0.1.jar
linkedin-dashlet-2.1.1.jar
twitter-dashlets-2.2.jar (timeline)
yammer-dashlet-2.1.jar

What version of Alfresco are you using? On what application server?
Alfresco 4.0.b, Ubuntu 11-10, 32 bits

What web browser are you using? Please supply browser name and version.
Firefox 7.0.1

Please provide any additional information below.
Same problem on Fedora 15

Original issue reported on code.google.com by jacobmde...@gmail.com on 2 Nov 2011 at 1:07

GoogleCodeExporter commented 8 years ago
Hi Jacob, the OAuth JAR actually needs to be placed in WEB-INF/lib inside both 
the Share and Alfresco webapps, due to the way Tomcat's classloader works. This 
should be clear in the docs but if it is not then please add a note to this 
ticket.

Original comment by will.abson on 7 Nov 2011 at 11:14

GoogleCodeExporter commented 8 years ago
Hi Will, that's not in the wiki. The wiki says "To install the add-on, simply 
drop the share-oauth.jar file into the tomcat/shared/lib folder". 
I've put the OAuth JAR in tomcat/webapps/alfresco/WEB-INF/lib and 
tomcat/webapps/share/WEB-INF/lib and now the Linkedin and Twitter dashlets are 
working fine.
Yammer asks for a verification code, which I don't have.

Original comment by jacobmde...@gmail.com on 8 Nov 2011 at 12:22

GoogleCodeExporter commented 8 years ago
Thanks for checking, Jacob. I've updated the wiki docs now so they should be 
accurate.

Regarding the Yammer dashlet, you should find that Yammer gives you this in a 
new window in your browser. I've updated the prompt text in SVN to make this 
slightly clearer.

Original comment by will.abson on 8 Nov 2011 at 10:15

GoogleCodeExporter commented 8 years ago
Hi Will,
Yammer is still not working, due to an authorization error. Maybe you cab help 
me figure this out..

The authorization of the dashlet gives an error.

A new window opens in the browser.
The URL = 
https://www.yammer.com/rotterdam.nl/oauth/invalid_client_application?client_appl
ication_id=4350
And the following is displayed: "Authorization Error
The application Share Extras can not be authorized in your network. Please 
contact your network administrator. Application Share Extras"

After closing the window, a popup comes up asking for the verification code
“Verification
Please enter the verification code from Yammer”

I don't know the code. Yammer is not connected. 

Maybe this is because we have a verified network for rotterdam.nl. Only people 
with a confirmed @rotterdam.nl email can join. What do you think? Should I 
contact Yammer?

Original comment by jacobmde...@gmail.com on 8 Nov 2011 at 8:45

GoogleCodeExporter commented 8 years ago
Hi Jacob, it seems a change is needed on the Yammer side to give the app access 
to other networks. We are working on this, but in the meantime you could always 
register your own application and override the default client key and secret 
specified in the META-INF/share-config-custom.xml file in the JAR with the 
values from your own app.

Original comment by will.abson on 12 Nov 2011 at 4:13

GoogleCodeExporter commented 8 years ago
Will, thaks for your update. I have no META-INF/share-config-custom.xml file. 
The share-config-custom.xml is in 
/shared/classes/alfresco/web-extension/share-config-custom.xml. Is that the 
correct file?
I need a little help to register yammer and override the default client key and 
secret. What's the code to do that?

Original comment by jacobmde...@gmail.com on 14 Nov 2011 at 12:43

GoogleCodeExporter commented 8 years ago
Hi Jacob, the share-config-custom.xml in META-INF should be inside the Yammer 
add-on JAR file. That is the file that contains the default connector and 
endpoint settings for the add-on, but it may be confusing that it has the same 
name as your local overrides file in shared/classes/alfresco/web-extension.

You should be able to override the default settings, if you add the following 
snippet to your overrides file.

    <config evaluator="string-compare" condition="Remote">
      <remote>
        <!-- Connector instance -->
        <connector>
            <id>yammer-oauth</id>
            <name>Yammer OAuth Connector</name>
            <description>HTTP Connector with support for OAuth authentication</description>
<class>org.sharextras.webscripts.connector.HttpOAuthConnector</class>
            <consumer-key>mykey</consumer-key>
            <consumer-secret>mysecret</consumer-secret>
            <signature-method>PLAINTEXT</signature-method>
        </connector>
      </remote>
    </config>

Original comment by will.abson on 14 Nov 2011 at 9:40

GoogleCodeExporter commented 8 years ago
Documented Yammer issue at 
http://code.google.com/p/share-extras/wiki/YammerDashlet#Known_Issues. Please 
add a comment there if you continue to have problems after testing. Otherwise 
I'll assume that the workaround works.

The main issue relating to the Share OAuth docs has been fixed, so I'm marking 
this issue as Fixed.

Original comment by will.abson on 28 Nov 2011 at 1:42