Encryption/Cryptography
PRB1411066
|
Sharing the cache across domains prevents the user from gaining access to
encrypted fields |
|
- As a user with elevated privileges, install the
com.glide.domain.msp_extensions.installer, com.glide.kmf.global, and
com.glide.encryption plugins.
- Install demo data on the Domain plugin and set the KMF property to
opt_in.
- Create a role and assign it to a new user (the user should be under ACME
domain) along with the incident_manager role.
- Create an encryption module, and use the module to create an encryption field
configuration.
- Create a module access policy with the module and role created above.
- Log in as the user created above and create an incident record.
- Clear the cache.
Expected behavior: The user should still have access to the
short_description column.
Actual behavior: The user does not have access to the short_description
column.
|
Encryption/Cryptography
PRB1412475
|
Pause and Resume are not working
correctly while running mass encryption or decryption jobs |
Jobs fail with the error 'Error creating job handler for type
module_field_encryption from serialized state : [No value present]'. |
- Activate the KMF and Encryption Support plugins.
- Set the sys_property to opt_in.
- Create an encryption module.
- Create an encrypted field config on the incident table and short description
column.
- Schedule a mass encryption job and set the time window.
For example, start
time - 14:00:00 and end time - 14:01:00.
- Start the scheduled job.
- Wait until the job interval end time window has passed.
The job state is
set to quiescent.
- Update the job window.
For example, start time - 14:05:00 and end time -
14:06:00.
- Click Update.
Expected behavior: The job should resume and continue processing the
remaining encrypted data.
Actual behavior: The job is not able to resume and fails with the error
'Error creating job handler for type module_field_encryption from serialized state
: [No value present]'.
|
Encryption/Cryptography
PRB1411669
|
Unable to create an encryption field config on a parent table after
deactivating a field config that was created on a child table |
|
- Log in as a user with elevated privileges and set the KMF property to
opt_in.
- Create an encryption module.
- Create a field configuration on the problem table (column: description).
- Create a field configuration on the task table.
Notice the errors 'Error
Message The selected field already has an encryption configuration for table
task or its extensions' and 'Error Message Invalid insert'.
- Open the field configuration on problem table and turn off the active
flag.
- Save the changes.
- Repeat step 4.
Expected behavior: The user should be able to create an encryption config
on the task table.
Actual behavior: The user is unable to replicate or create an encryption
config on the task table. They receive the errors 'Error Message The selected
field already has an encryption configuration for table task or its extensions'
and 'Error Message Invalid insert'.
|
Encryption/Cryptography
PRB1396485
|
Global search does not work during or after the CLE to KMF and KMF to CLE
migration phases |
After upgrading a New York instance to Orlando, global search no longer finds
terms in encrypted fields. |
- Activate the CLE and KMF plugins.
- Configure the CLE context, role, and user.
- Log in as a user and trigger the mass encryption of a test field (for example,
incident.short_description).
- After encryption is finished, use global search to find terms in the test
field.
The terms should be found.
- Modify the glide_encryption.cle_ replatforming_with_kmf property value to
opt_in.
- Execute gs.cacheFlush(); from Scripts - Background.
- Log out, then log back in as a user with elevated privileges.
- Run the key migration (context to module) scheduled job.
- Run the data migration (context to module) scheduled job.
- Log in as the first user and search for same terms as before the migration to
module encryption.
Expected behavior: The test terms should be found.
Actual behavior: The test terms are not found.
|
MID Server
PRB1411493
|
PowerShell processes leak while importing modules |
After spinning up a PowerShell process, it is used to load modules and run
commands. In case it hits the timeout while loading the modules, the process is
never closed. The default is a 1-minute timeout for loading modules. |
|