Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Encryptor.decrypt can choke if you pass in a null key

Description

Startup the portal with an IBM JDK, now Company.key is using the default IBM JDK provider.

Now start the portal with a Sun JDK, company.getKey() is null because it can't read the value from the Company.key table since it is a key that is using a provider that is not supported.

Try signing in, big NullPointerException because bottom_js.jsp chokes on:

encryptedUserId: '<%= Encryptor.encrypt(company.getKeyObj(), String.valueOf(themeDisplay.getUserId())) %>',

This simply allows things to work and prints a warning. This should only happen in tests scenarios. Most ppl don't swap JDKs in production.

Activity

Show:

Michael SaechangJune 28, 2012 at 2:43 PM

Committed on:
Portal 6.1.x CE GIT ID: 1fdb01b6037393f85b0dc35a2cc49970e95c04d3.
Portal 6.2.x GIT ID: cc55cf56c9e19b1e1bc92bf21876c3ec015cea43.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Branch Version/s

6.1.x

Backported to Branch

Committed

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created June 1, 2012 at 12:56 PM
Updated June 24, 2023 at 3:50 PM
Resolved June 1, 2012 at 1:15 PM