what is the packet structure in kerberos after authorization?
up vote
0
down vote
favorite
I read this article https://www.roguelynn.com/words/explain-like-im-5-kerberos/ and got a good understanding what are kerberos authentication packets like.
But nobody mention how the further packets look like, after authorization ends. Do they have client id in their headers or some numbers that will help to identify what user is sending this packet? If not, how do we determine on the other side (server side) which key to decrypt should we use (as we can have multiple users at once in a single connection).
In this article it is only said :
Future requests use the cached HTTP Service Ticket, so long as it has not expired as defined within the lifetime attribute.
P.S. assume we have kerberos over tcp.
authentication kerberos
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
add a comment |
up vote
0
down vote
favorite
I read this article https://www.roguelynn.com/words/explain-like-im-5-kerberos/ and got a good understanding what are kerberos authentication packets like.
But nobody mention how the further packets look like, after authorization ends. Do they have client id in their headers or some numbers that will help to identify what user is sending this packet? If not, how do we determine on the other side (server side) which key to decrypt should we use (as we can have multiple users at once in a single connection).
In this article it is only said :
Future requests use the cached HTTP Service Ticket, so long as it has not expired as defined within the lifetime attribute.
P.S. assume we have kerberos over tcp.
authentication kerberos
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I read this article https://www.roguelynn.com/words/explain-like-im-5-kerberos/ and got a good understanding what are kerberos authentication packets like.
But nobody mention how the further packets look like, after authorization ends. Do they have client id in their headers or some numbers that will help to identify what user is sending this packet? If not, how do we determine on the other side (server side) which key to decrypt should we use (as we can have multiple users at once in a single connection).
In this article it is only said :
Future requests use the cached HTTP Service Ticket, so long as it has not expired as defined within the lifetime attribute.
P.S. assume we have kerberos over tcp.
authentication kerberos
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
I read this article https://www.roguelynn.com/words/explain-like-im-5-kerberos/ and got a good understanding what are kerberos authentication packets like.
But nobody mention how the further packets look like, after authorization ends. Do they have client id in their headers or some numbers that will help to identify what user is sending this packet? If not, how do we determine on the other side (server side) which key to decrypt should we use (as we can have multiple users at once in a single connection).
In this article it is only said :
Future requests use the cached HTTP Service Ticket, so long as it has not expired as defined within the lifetime attribute.
P.S. assume we have kerberos over tcp.
authentication kerberos
authentication kerberos
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
asked Nov 22 at 16:20
Anastasiya Ruzhanskaya
136118
136118
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53434921%2fwhat-is-the-packet-structure-in-kerberos-after-authorization%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
