My Oracle Support Banner

E1: BSSV: E1BSSVAuthenticator.jar fails to create on the Provider tab in Weblogic Server 10.3.x (E1BSSVAuthenticatorV2.jar - TR 9.1.4.x and Above) (Doc ID 1470910.1)

Last updated on SEPTEMBER 10, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Purpose

The E1BSSVAuthenticator (or V2) is not getting installed during the deployment of the BSSV package. It is missing in the Provider list in WLS console (Security Realms::myrealm::Provider Tab).

This document contains some common symptoms and possible solutions

Scope

 

Details

To view full details, sign in with your My Oracle Support account.

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

In this Document
Purpose
Scope
Details
 Symptom:  The E1BSSVAuthenticor.jar (or V2) is not showing on the provider tab.
 Symptom:  BSSV custom authentication provider could not be set up. This is likely due to one or more WebLogic managed servers that were running.
 Symptom: With the Agent logging level set to FINEST/ALL search for "configureJAASAuthenticator" and if the statement is not found, E1BSSVAuthenticator will not be installed
 Symptom: SM agent doesn’t seem to be connecting to the admin server(s) most of the time.
 Symptom:  Message in E1agent.log states E1 BSSV custom authentication provider could not be set up. 
 How to manually install the E1BSSVAuthenticator or E1BSSVAuthenticatorV2 (TR 9.1.4.x+).
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.