According to the KdcProxy docs, the configuration should have a kpasswd_server entry. It will enable the necessary password change flow for users with an expired password, and prevent issues such as noggin #895.
kpasswd_server
Without this value:
$ kinit -T FILE:/tmp/armor.ccache abompard@STG.FEDORAPROJECT.ORG Enter OTP Token Value: [password+OTP] Password expired. You must change it now. Enter new password: [new password] Enter it again: [new password] kinit: Cannot find KDC for realm "STG.FEDORAPROJECT.ORG" while getting initial credentials
With this value:
$ kinit -T FILE:$HOME/armor.ccache abompard@STG.FEDORAPROJECT.ORG Enter OTP Token Value: [password+OTP] Password expired. You must change it now. Enter new password: [new password] Enter it again: [new password] Enter OTP Token Value: [password+OTP]
Huh. I thought this wouldn't work with OTP... but it sounds like it does?
If so, +1 from me.
Is there also a DNS entry for kpasswd server we should add?
The updated krb5 config with a defined kpasswd_server let me unlock my account. The web password reset flow is still having issues. I've updated my comments in the Github issue.
There is one clarifying item here:
init -T FILE:$HOME/armor.ccache user@REALM Enter OTP Token Value: [current password+OTP] Password expired. You must change it now. Enter new password: [new password] Enter it again: [new password] Enter OTP Token Value: [new password+OTP]
Lets go ahead and merge this.
Pull-Request has been merged by kevin
According to the KdcProxy docs, the configuration should have a
kpasswd_serverentry. It will enable the necessary password change flow for users with an expired password,and prevent issues such as noggin #895.
Without this value:
With this value: