-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Secretserver develop #1092
Secretserver develop #1092
Conversation
Codecov ReportBase: 64.57% // Head: 64.55% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1092 +/- ##
===========================================
- Coverage 64.57% 64.55% -0.03%
===========================================
Files 541 541
Lines 50910 50926 +16
===========================================
Hits 32877 32877
- Misses 18033 18049 +16
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -14,28 +14,21 @@ | |||
} | |||
}, | |||
|
|||
"user-account": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove this and stick it in a custom object? When possible, standard STIX objects should be used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done the changes
"x-secret": { | ||
"fields": { | ||
"secret_name": ["SecretName"], | ||
"user_name": ["username"], | ||
"username": ["EmailAddress"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is an email address, it should go under the email-addr:value
property.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"x-secret": { | ||
"fields": { | ||
"secret_name": ["SecretName"], | ||
"user_name": ["username"], | ||
"username": ["Unique_Identtification"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't this go in user-account:display_name
instead of this custom object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have done our db parser changes with the above mapping. If it is not mandatory, Can it be taken for next release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is Unique_Identification different from the username field? This can likely remain where it is if they are different.
"secret_id": ["ItemId"], | ||
"user_id": ["UserId"] | ||
"user_id": ["UserId"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this not just in the user-account:user_id
object? No need to put it in a custom object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
"x-secret": { | ||
"fields": { | ||
"secret_name": ["SecretName"], | ||
"username": ["EmailAddress"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in a email-addr:value
property and not a custom object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
"secret_name": ["SecretName"], | ||
"username": ["EmailAddress"], | ||
"secret_id": ["ItemId"], | ||
"user_id": ["UserId"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in a user-account:user_id
property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
"username": ["EmailAddress"], | ||
"secret_id": ["ItemId"], | ||
"user_id": ["UserId"], | ||
"server_user_name" : ["Username"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in a user-account:display_name
property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have done our db parser changes with the above mapping. If it is not mandatory, Can it be taken for next release?
"user_id": [ | ||
"UserId" | ||
] | ||
"user_name": ["username"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This property needs to be display_name
, there is no user_name
property on the user-account object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done the changes
{ | ||
"username": [ | ||
{ | ||
"key": "user-account.user_name" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be user-account.display_name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done the changes
No description provided.