Mainly the reason is that theproject has some requirements from customer to encrypt and restrict the access to certain requirement modules.
So, a part of locking those modules with a password or something similar, we need to encrypt them. With the encryption, we can protect the confidentiality of those modules in case the access protection mechanism (password) fails.
Encryption is basically encoding the content of those modules to be unreadable for someone that get unauthorized access to them.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPERNov 25 '22, 6:57 a.m.
While servers often support whole disk encryption, and data in motion is encrypted using HTTPS, your real requirement seems to be one of read access. The way to control who has read access to requirements is to use a project area with read access limited to the subset of users who need to see its artifacts and use that project area for such sensitive requirements.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPERNov 25 '22, 9:50 a.m.
Having account dependent visibility is absolute industry standard - if implemented at all. Why on earth would one want another password? How many would you want? Who would know them? Would you have them on post-its on the display? This would be the major complaint from the users that the usability is crap, I am sure.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Nov 21 '22, 3:18 a.m.Why would you want to do that?
Daniel Moul
FORUM MODERATOR / JAZZ DEVELOPER Nov 21 '22, 8:03 a.m.Or to ask the same question in more words and to provide some answers...
khalid INU
Nov 25 '22, 5:03 a.m.Hello all,
Thank you for your response,
Mainly the reason is that the project has some requirements from customer to encrypt and restrict the access to certain requirement modules.
So, a part of locking those modules with a password or something similar, we need to encrypt them. With the encryption, we can protect the confidentiality of those modules in case the access protection mechanism (password) fails.
Encryption is basically encoding the content of those modules to be unreadable for someone that get unauthorized access to them.
David Honey
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Nov 25 '22, 6:57 a.m.While servers often support whole disk encryption, and data in motion is encrypted using HTTPS, your real requirement seems to be one of read access. The way to control who has read access to requirements is to use a project area with read access limited to the subset of users who need to see its artifacts and use that project area for such sensitive requirements.
1 vote
khalid INU
Nov 25 '22, 8:22 a.m.Allright, I see
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Nov 25 '22, 9:50 a.m.Having account dependent visibility is absolute industry standard - if implemented at all. Why on earth would one want another password? How many would you want? Who would know them? Would you have them on post-its on the display? This would be the major complaint from the users that the usability is crap, I am sure.