IBM Connections: userid vs key - Why has connection multiple identifier for a single user?
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
asked Nov 21 '18 at 7:55
DanielDaniel
107111
add a comment |
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
asked Nov 21 '18 at 7:55
DanielDaniel
107111
add a comment |
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
asked Nov 21 '18 at 7:55
DanielDaniel
107111
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 Nov 21 '18 at 7:55
DanielDaniel
107111
asked Nov 21 '18 at 7:55
DanielDaniel
107111
asked Nov 21 '18 at 7:55
DanielDaniel
107111
asked Nov 21 '18 at 7:55
DanielDaniel
107111
asked Nov 21 '18 at 7:55
DanielDaniel
107111
107111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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 Nov 21 '18 at 8:04
umeliumeli
670513
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 Nov 21 '18 at 8:04
umeliumeli
670513
add a comment |
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 Nov 21 '18 at 8:04
umeliumeli
670513
add a comment |
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 Nov 21 '18 at 8:04
umeliumeli
670513
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 Nov 21 '18 at 8:04
umeliumeli
670513
answered Nov 21 '18 at 8:04
umeliumeli
670513
answered Nov 21 '18 at 8:04
umeliumeli
670513
answered Nov 21 '18 at 8:04
umeliumeli
670513
670513
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
