IBM Connections: userid vs key - Why has connection multiple identifier for a single user?
up vote
0
down vote
favorite
When I look at the source of a profile page like https://<connections-host>/profiles/html/profileView.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
I see two kind of ids in the page source:
profilesData.displayedUser = {
key: "7a74e3bf-6cf4-40cd-a593-801275661353",
dn: "<dn>",
displayName: "Alice Someone",
userid:"98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8",
// ...
};
userid
seems like a regular GUID for the user, that's clear for me. But why do we have an additional key
attribute? It also looks like another GUID but lowercase.
Connections API
The reason why I'm asking is: IBM's User API asks for a key
attribute, e.g. /profiles/atom/profileEntry.do?key=7a74e3bf-6cf4-40cd-a593-801275661353
. We can also call /profiles/atom/profileEntry.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
, altough this is not official documentated.
Can someone explain why we have two ids? And what is the reason for using key
instead of userid
here? It disagrees the concept of an id to be unique.
api guid ibm-connections id
add a comment |
up vote
0
down vote
favorite
When I look at the source of a profile page like https://<connections-host>/profiles/html/profileView.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
I see two kind of ids in the page source:
profilesData.displayedUser = {
key: "7a74e3bf-6cf4-40cd-a593-801275661353",
dn: "<dn>",
displayName: "Alice Someone",
userid:"98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8",
// ...
};
userid
seems like a regular GUID for the user, that's clear for me. But why do we have an additional key
attribute? It also looks like another GUID but lowercase.
Connections API
The reason why I'm asking is: IBM's User API asks for a key
attribute, e.g. /profiles/atom/profileEntry.do?key=7a74e3bf-6cf4-40cd-a593-801275661353
. We can also call /profiles/atom/profileEntry.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
, altough this is not official documentated.
Can someone explain why we have two ids? And what is the reason for using key
instead of userid
here? It disagrees the concept of an id to be unique.
api guid ibm-connections id
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I look at the source of a profile page like https://<connections-host>/profiles/html/profileView.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
I see two kind of ids in the page source:
profilesData.displayedUser = {
key: "7a74e3bf-6cf4-40cd-a593-801275661353",
dn: "<dn>",
displayName: "Alice Someone",
userid:"98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8",
// ...
};
userid
seems like a regular GUID for the user, that's clear for me. But why do we have an additional key
attribute? It also looks like another GUID but lowercase.
Connections API
The reason why I'm asking is: IBM's User API asks for a key
attribute, e.g. /profiles/atom/profileEntry.do?key=7a74e3bf-6cf4-40cd-a593-801275661353
. We can also call /profiles/atom/profileEntry.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
, altough this is not official documentated.
Can someone explain why we have two ids? And what is the reason for using key
instead of userid
here? It disagrees the concept of an id to be unique.
api guid ibm-connections id
When I look at the source of a profile page like https://<connections-host>/profiles/html/profileView.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
I see two kind of ids in the page source:
profilesData.displayedUser = {
key: "7a74e3bf-6cf4-40cd-a593-801275661353",
dn: "<dn>",
displayName: "Alice Someone",
userid:"98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8",
// ...
};
userid
seems like a regular GUID for the user, that's clear for me. But why do we have an additional key
attribute? It also looks like another GUID but lowercase.
Connections API
The reason why I'm asking is: IBM's User API asks for a key
attribute, e.g. /profiles/atom/profileEntry.do?key=7a74e3bf-6cf4-40cd-a593-801275661353
. We can also call /profiles/atom/profileEntry.do?userid=98A10FD8-FCC3-5DD7-C125-6A9B0055D8C8
, altough this is not official documentated.
Can someone explain why we have two ids? And what is the reason for using key
instead of userid
here? It disagrees the concept of an id to be unique.
api guid ibm-connections id
api guid ibm-connections id
asked 4 hours ago
Daniel
91110
91110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Connections is built from several different apps with different databases (People, Blogs, Homepage, ....). Each DB has its own user table with their own keys. The second id is the userid, which should be the same across all DBs.
In your example, the key refers to the peopledb. It's only valid in the profiles app.
The Userid is valid accross all connections apps.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Connections is built from several different apps with different databases (People, Blogs, Homepage, ....). Each DB has its own user table with their own keys. The second id is the userid, which should be the same across all DBs.
In your example, the key refers to the peopledb. It's only valid in the profiles app.
The Userid is valid accross all connections apps.
add a comment |
up vote
1
down vote
accepted
Connections is built from several different apps with different databases (People, Blogs, Homepage, ....). Each DB has its own user table with their own keys. The second id is the userid, which should be the same across all DBs.
In your example, the key refers to the peopledb. It's only valid in the profiles app.
The Userid is valid accross all connections apps.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Connections is built from several different apps with different databases (People, Blogs, Homepage, ....). Each DB has its own user table with their own keys. The second id is the userid, which should be the same across all DBs.
In your example, the key refers to the peopledb. It's only valid in the profiles app.
The Userid is valid accross all connections apps.
Connections is built from several different apps with different databases (People, Blogs, Homepage, ....). Each DB has its own user table with their own keys. The second id is the userid, which should be the same across all DBs.
In your example, the key refers to the peopledb. It's only valid in the profiles app.
The Userid is valid accross all connections apps.
answered 4 hours ago
umeli
595311
595311
add a comment |
add a comment |
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407458%2fibm-connections-userid-vs-key-why-has-connection-multiple-identifier-for-a-si%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown