Question regarding 401 Error about yammer-plugin

[flopo33]

Hi there,
same problem in here

• Access Token is available, and some GET calls in browser are working
• Ruby and Rails are installed on Jenkins Server
• User is Admin from Group

Only the Jenkins service is started with a different User as the yammer user, but i think this is not a problem.

@jsharifi: is your problem solved or do you have any other ideas?

[jsharifi]

Hi @flopo33, it appears Yammer has changed how apps authenticate, basically breaking existing apps. What I've decided to do instead is use the Jenkins Email-Ext plugin to send an email in the format of "[email protected]". This will post messages just like the Yammer plugin. The reason I'm using the Email-Ext plugin is because the default Jenkins email functionality only sends an email on failure. Hope this helps.

[bvarner]

I just found this plugin and decided to give it a try. After going through the trouble of getting all the auth bits to work properly, I'm really really disappointed to see the 401 issue as well.

[flopo33]

Hi @jsharifi: that's a good idea and workaround.
the standard email functionality also sends on failure in my case.
so i tried Email-Ext but it also returns failure.

Error sending to the following INVALID addresses: [email protected]

Is it caused by the ".de" or what do you think? Any ideas?

[jsharifi]

@flopo33 we had a similar problem with our old smtp relay server because it didn't recognize an email address with a "+" in it as valid.