Configure Users to Be Able to Login with SSO (Kerberos) in the Java Client but Also Being Able to Login to the Web Client (Doc ID 1981428.1)

Last updated on AUGUST 11, 2016

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Kerberos users mapped for Single Sign On (SSO) Login cannot access the application using the Web Client or the Web Development Toolkit respectively (login denied).
It is necessary to configure users so that they are able to access the application with Kerberos using the Java Client and with LDAP or Standard-Login using the Web Client / The Web Development Toolkit

Expected Behavior:
============
If a user is configured for Kerberos access, he or she should be able to login using the Web Client or the Web Development Toolkit. It is not necessary that this works through Kerberos as well but a "Standard-Login" or a LDAP-Login has to work.


The issue can be reproduced at will with the following steps:
====================================
1. Configure a user in the user data mask that it uses SSO (Kerberos) for accessing the application
2. Start the application with the Java Client to verify the SSO-login works as expected
3. Try to launch the application with the same user from the Web Client or from the Web Development Toolkit
=> User cannot login because Kerberos is not supported in those clients


Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms