Data source authentication
Some data sources require authentication to access the
data on a protected server. When Rational® Publishing Engine has
to retrieve data from a protected server, each authentication type
is tested automatically until the correct one for the data source
is found. Instead of waiting for each type to be tested, you can specify
authentication types in templates and document specifications with
your credentials so you do not have to wait for Rational Publishing Engine to
test each authentication type.
Authentication types
You can enter one of
these case-sensitive authentication types in the authentication property
for a data source in a template or document specification:
- Form
- Basic
- OAuth-OSLCNote: You can specify OAuth-OSLC authentication for Generic XML, REST v1, REST v2 data sources.
- OAuthNote:
- Rational Publishing Engine supports OAuth authentication types that are specific to Jazz™ products.
- If OAuth authentication is specified, Rational Publishing Engine handles the authentication as OAuth1a.
If you do not enter an authentication type or enter auto in Document Studio, each type is tested in the order above until the correct type is found and then cached as the authentication type setting for future connections within a current document generation. For subsequent document generation, even when running in the same Launcher or Document Studio instance, the initial auto connection repeats the process by once again testing each type to find and cache the correct type.
Improve performance by specifying the authentication type
You can improve document generation performance by:- Specifying the authentication type when you add a data source schema to a template.
- Specifying the authentication type for a data source in a document specification.
Note: For data sources that support only OAuth1a,
you must set the authentication property to OAuth explicitly.
An auto-detection algorithm results in failure and the OAuth cannot
be verified. This failure occurs because the OAuth1a algorithm falsely
reports authentication success. The auto algorithm
stops, but the data that is accessed is actually the login page itself
and not the real data.