3 Known Issues

The following table lists the known issues in this release and the workaround for each issue.

Table 3-1 Known Bugs in this Release

BugID Description
38088650

Adding or editing specific configuration with respect to the newly created authentication providers is not possible, due to the missing “Provider Specific” tab/slice in this release, which will be termed as “Custom Parameters” going forward in the upcoming Remote Console release.

The following types of authentication providers are missing the Custom Parameters tab:
  • DBMS Digest Identity Asserter
  • PAsserted Identity Asserter
  • PAsserted Identity Strict Asserter
  • X3gpp Asserted Identity Asserter
  • X3gpp Asserted Identity Strict Asserter
  • Identity Assertion Authenticator
  • Identity Header Asserter
  • Ldap Digest Identity Asserter

For a workaround, see the Workarounds section.
38059951 In the hosted Remote Console, the "Create" option does not show options for creating an entry in the "Map by Router" section under Profile Service – Diameter Domain
38065383 On modifying any property that requires restart, there is no banner on the Remote Console informing the user that "Restart may be required for property change to be effective." However across that property there is an icon which indicates "Server or App Restart is required."
37975561 Error Message pops up (UnExpected Error Response) when clicking Sip Application RunTime, and then Deployed Application name.
37942688 Under Custom Resources, and then sipserver, and then SIP Server, there is no page which displays the "Targets" fields. This page identifies the servers or clusters to which the Converged Application Server configuration is targeted.

20742195

The RFC 6665 specification states that proxy servers that do not add Record-Route header fields to the initial SUBSCRIBE request are then prohibited from adding Record-Route header fields to any associated NOTIFY requests. However, Converged Application Server does not check for Record-Route header fields in NOTIFY requests.

Developers creating applications for Converged Application Server should not call Proxy.setRecordRoute(true), or proxyBranch.setRecordRoute(true) when handling notify requests that did not already set the Record-Route header field in a Register request.
20318523 / 20550145

Associating too many sessions with a single key causes performance problems.

When using the new SipApplicationSession addIndexKey() method, ensure that the session keys you create are unique to subscribers. This strategy helps you avoid performance degradation problems.

If your session keys are unique to subscribers and large reads still cause performance problems, try paging the result when iterating over the read index record.

If your session keys are unique to subscribers and large writes still cause performance problems, try splitting large index records into smaller "chunks." That way you do not need to deserialize the full record to add or remove values from it.
18066581

Deploying SIP applications that declare ServletContainerInitializer can in some cases cause the onStartup() method to be called twice.

You can prevent this by using the wlss.initializer.classes system property to specify and limit SIP specific container initializers.
15957604

Applications should not try to inject a resource with the same name in both a field and method. For example, injecting a SipFactory resource with the same name into both the setMySipFactory method and the mySipFactory field is not supported.

This behavior is prohibited by JavaEE specification EE.5.2.3, but this release of Converged Application Server does not specifically check for this error.

Violating this rule can cause unexpected behavior.

Workarounds

As a workaround for issue 38088650, first navigate to Security, and then Realms, and then your realm, and then Authentication Providers. Create a new provider and provide details about the Name and Type. Next, switch to the REST API or WLST to configure specific attributes.

For example, to configure with the REST API, fetch the list of providers from this endpoint: .

http://<hostname>:<port>/management/weblogic/latest/edit/securityConfiguration/realms/myrealm/authenticationProviders/

Next add or update the configuration using this endpoint: .

http://<hostname>:<port>/management/weblogic/latest/edit/securityConfiguration/realms/myrealm/authenticationProviders/MyAuthProvider

Replace <hostname> with the hostname or IP address of your webserver, and replace <port> with the port that the Admin Server listens on.

By contrast, to configure using WLST, you might run this script:

startEdit()
cd('/SecurityConfiguration/replicatedOccasDomain/Realms/myrealm/AuthenticationProviders/MyAuthProvider)
set('TrustedHosts',jarray.array([String(‘trustedHostedNames’)], String))
activate()