RPE 1.3 OAuth problem


If you have upgraded to RPE 1.3 and you are experiencing login failures when connecting to data sources that use OAuth ( such as DNG) please follow the links below for more details and a the workaround you can use until a fix is made available.

http://www.ibm.com/support/docview.wss?uid=swg21690434

https://www.ibm.com/developerworks/community/forums/html/topic?id=5a3af5bb-1bda-4314-aa12-90886e883c09&ps=25

UPDATE 2014.11.21

The workaround is to avoid some special characters in your password. Not all special characters are causing this problem, only those that need to be URL encoded such as “:”, “/”. “%” are. To determine if a character has to be encoded or not you can use online tools such as this one:

http://www.opinionatedgeek.com/DotNet/Tools/UrlEncode/Encode.aspx

If a character remains unchanged in the”Encoded output” tab  than it can be used in the password without triggering the defect.

This is just a temporary workaround, we will provide a fix for this problem soon.

Advertisements

Author: Dragos Cojocari

Architect for Rational Publishing Engine

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s