Bug #84487 InnoDB does not use tblspace id to manage tablespace encryption keys in keyring
Submitted: 12 Jan 2017 13:22 Modified: 13 Jan 2017 15:38
Reporter: Laurynas Biveinis (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any
Tags: doc, innodb, keyring, TDE

[12 Jan 2017 13:22] Laurynas Biveinis 
Description:
https://dev.mysql.com/doc/refman/5.7/en/keyring-service.html describes the key id pair (key_id; user_id) as follows for the user_id part:

"user_id: The session effective user ID. If there is no user context, this value can be NULL. The value need not actually be a “user”; for example, InnoDB uses tablespace IDs to manage keys for tablespaces."

By code review the "for example" part seems wrong:
- InnoDB does not use keyring to manage the tablespace keys at all, the keyring is used only for the instance master key;
- A tablespace ID is never passed as user_id to the keyring API. For the master key it does not make sense anyway, and NULL is passed there.

How to repeat:
Read docs

Suggested fix:
Fix docs
[13 Jan 2017 4:59] MySQL Verification Team 
Hello Laurynas,

Thank you for the report and feedback!

Thanks,
Umesh
[13 Jan 2017 15:38] Paul DuBois 
Posted by developer:
 
Will change it to "the meaning depends on the application."