Add new attribute to IPA user info (Linux)
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I am not sure its so straightforward on the Linux side.
I want to add a new attribute to identify users as Contractor or Government.
Is this recommended or possible within LDAP?
linux rhel users ldap freeipa
add a comment |Â
up vote
1
down vote
favorite
I am not sure its so straightforward on the Linux side.
I want to add a new attribute to identify users as Contractor or Government.
Is this recommended or possible within LDAP?
linux rhel users ldap freeipa
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.
â KevinO
Jul 18 at 14:43
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am not sure its so straightforward on the Linux side.
I want to add a new attribute to identify users as Contractor or Government.
Is this recommended or possible within LDAP?
linux rhel users ldap freeipa
I am not sure its so straightforward on the Linux side.
I want to add a new attribute to identify users as Contractor or Government.
Is this recommended or possible within LDAP?
linux rhel users ldap freeipa
asked Jul 18 at 14:13
Mervyn Clarke
184
184
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.
â KevinO
Jul 18 at 14:43
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49
add a comment |Â
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.
â KevinO
Jul 18 at 14:43
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,
inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.â KevinO
Jul 18 at 14:43
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,
inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.â KevinO
Jul 18 at 14:43
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457008%2fadd-new-attribute-to-ipa-user-info-linux%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
It is certainly possible to modify the LDAP schema to add an attribute, assuming that a suitable attribute in a class does not already exist. For example,
inetOrgPerson
already has "employee type" which might be suitable. However, you could also model the domain differently (using a different/additional OU for example), or perhaps just using groups. I think providing a few scenarios about how you want to filter/search, etc. would help.â KevinO
Jul 18 at 14:43
Thank you. For example: ipa user-show jdoe -all would show a field of Status: Contractor or Status: Government.
â Mervyn Clarke
Jul 18 at 14:49