Wrong start and expire date in credentials cache after kerberos auth
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I log in to Ubuntu 18.04 successfully with kerberos/sssd authentification in an ActiveDirectory domain.
Since a few days I have an issue using my kerberos ticket/credentials cache to auth with some server shares.
If i call klist my credentials cache is displayed with start and expire date 01.01.1970. I believe that this causes my issue.
After removing /tmp/krb5cc-file and authenticating with kinit again the start and expire date is correct and auth against server shares work like expected.
Do you know about known issues causing this behaviour?
Or any hints how to solve this without double authenticate?
Some of my colleagues are working with 18.04 too but without any issues.
Best regards
Patrick
18.04 authentication kerberos sssd
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
add a comment |
I log in to Ubuntu 18.04 successfully with kerberos/sssd authentification in an ActiveDirectory domain.
Since a few days I have an issue using my kerberos ticket/credentials cache to auth with some server shares.
If i call klist my credentials cache is displayed with start and expire date 01.01.1970. I believe that this causes my issue.
After removing /tmp/krb5cc-file and authenticating with kinit again the start and expire date is correct and auth against server shares work like expected.
Do you know about known issues causing this behaviour?
Or any hints how to solve this without double authenticate?
Some of my colleagues are working with 18.04 too but without any issues.
Best regards
Patrick
18.04 authentication kerberos sssd
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29
add a comment |
I log in to Ubuntu 18.04 successfully with kerberos/sssd authentification in an ActiveDirectory domain.
Since a few days I have an issue using my kerberos ticket/credentials cache to auth with some server shares.
If i call klist my credentials cache is displayed with start and expire date 01.01.1970. I believe that this causes my issue.
After removing /tmp/krb5cc-file and authenticating with kinit again the start and expire date is correct and auth against server shares work like expected.
Do you know about known issues causing this behaviour?
Or any hints how to solve this without double authenticate?
Some of my colleagues are working with 18.04 too but without any issues.
Best regards
Patrick
18.04 authentication kerberos sssd
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
I log in to Ubuntu 18.04 successfully with kerberos/sssd authentification in an ActiveDirectory domain.
Since a few days I have an issue using my kerberos ticket/credentials cache to auth with some server shares.
If i call klist my credentials cache is displayed with start and expire date 01.01.1970. I believe that this causes my issue.
After removing /tmp/krb5cc-file and authenticating with kinit again the start and expire date is correct and auth against server shares work like expected.
Do you know about known issues causing this behaviour?
Or any hints how to solve this without double authenticate?
Some of my colleagues are working with 18.04 too but without any issues.
Best regards
Patrick
18.04 authentication kerberos sssd
18.04 authentication kerberos sssd
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
asked Dec 20 '18 at 7:18
pfleckensteinpfleckenstein
314
314
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29
add a comment |
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29
add a comment |
2 Answers
2
active
oldest
votes
I identified the issue.
Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
add a comment |
I had a similar issue with my local Single Sign-On environment (not AD but OpenLDAP + MIT Kerberos) after I re-installed Ubuntu 18.04. For me, configuring sssd to automatically renew tickets resolved the issue. I just had to add the following lines to sssd.conf and restart the sssd service.
[domain/MY_REALM_NAME]
...
krb5_renewable_lifetime = 7d
krb5_renew_interval = 30m
...
answered 6 mins ago
cqcallawcqcallaw
9281818
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1103280%2fwrong-start-and-expire-date-in-credentials-cache-after-kerberos-auth%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I identified the issue.
Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
add a comment |
I identified the issue.
Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
add a comment |
I identified the issue.
Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
I identified the issue.
Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
answered Dec 27 '18 at 8:00
pfleckensteinpfleckenstein
314
314
add a comment |
add a comment |
I had a similar issue with my local Single Sign-On environment (not AD but OpenLDAP + MIT Kerberos) after I re-installed Ubuntu 18.04. For me, configuring sssd to automatically renew tickets resolved the issue. I just had to add the following lines to sssd.conf and restart the sssd service.
[domain/MY_REALM_NAME]
...
krb5_renewable_lifetime = 7d
krb5_renew_interval = 30m
...
answered 6 mins ago
cqcallawcqcallaw
9281818
add a comment |
I had a similar issue with my local Single Sign-On environment (not AD but OpenLDAP + MIT Kerberos) after I re-installed Ubuntu 18.04. For me, configuring sssd to automatically renew tickets resolved the issue. I just had to add the following lines to sssd.conf and restart the sssd service.
[domain/MY_REALM_NAME]
...
krb5_renewable_lifetime = 7d
krb5_renew_interval = 30m
...
answered 6 mins ago
cqcallawcqcallaw
9281818
add a comment |
I had a similar issue with my local Single Sign-On environment (not AD but OpenLDAP + MIT Kerberos) after I re-installed Ubuntu 18.04. For me, configuring sssd to automatically renew tickets resolved the issue. I just had to add the following lines to sssd.conf and restart the sssd service.
[domain/MY_REALM_NAME]
...
krb5_renewable_lifetime = 7d
krb5_renew_interval = 30m
...
answered 6 mins ago
cqcallawcqcallaw
9281818
I had a similar issue with my local Single Sign-On environment (not AD but OpenLDAP + MIT Kerberos) after I re-installed Ubuntu 18.04. For me, configuring sssd to automatically renew tickets resolved the issue. I just had to add the following lines to sssd.conf and restart the sssd service.
[domain/MY_REALM_NAME]
...
krb5_renewable_lifetime = 7d
krb5_renew_interval = 30m
...
answered 6 mins ago
cqcallawcqcallaw
9281818
answered 6 mins ago
cqcallawcqcallaw
9281818
answered 6 mins ago
cqcallawcqcallaw
9281818
answered 6 mins ago
cqcallawcqcallaw
9281818
9281818
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1103280%2fwrong-start-and-expire-date-in-credentials-cache-after-kerberos-auth%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
Could this be your "issue"? bugs.launchpad.net/ubuntu/+source/sssd/+bug/1039151
– Sebastian Stark
Dec 20 '18 at 9:59
Thanks. I checked this. But this seems to be another bug. Regardless how long I wait for login expire dates are always wrong. So it seems that my issue is not a network related bug. During testing I recognised that if I turn off password caching I am not able to login any more...
– pfleckenstein
Dec 21 '18 at 11:45
But maybe an sssd related one? Have you tried without support for offline login?
– Sebastian Stark
Dec 21 '18 at 11:48
I identified the issue. Seems that something was wrong with my computer account stored in Active Directory. In my case strangely it was missing. Added it with net ads join now everything works like expected. Thanks for your support!
– pfleckenstein
Dec 21 '18 at 12:03
you can answer.your own question then if you like
– Sebastian Stark
Dec 21 '18 at 12:29