Ticket #1436 (closed defect: fixed)
Update krb5.conf to include domain mapping for EXCHANGE
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Current Semester |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | kerberos-config 1.18 | |
| Upstream bug: |
Description
Now that Exchange supports GSSAPI, we should add a domain mapping to krb5.conf so it "just works".
Change History
comment:2 in reply to: ↑ 1 Changed 11 years ago by andersk
Replying to jdreed:
Also, Ben says we should remove the ".domain" mappings. For future generations, we could replace them with a comment noting that they are only needed if the host should have a different REALM mapping than other hosts under that domain.
Our [domain_realm] section comes from krb5-config upstream, so if we want that to do any good, we should get it fixed there.
We might as well tell upstream about EXCHANGE.MIT.EDU (and WIN.MIT.EDU, which is the only other thing we add), too, but obviously we’ll still need in the Debathena package for current releases.
comment:4 Changed 11 years ago by jdreed
- Status changed from review to committed
committed 33a6c75d30d1092f4f78f70e5f06ecbda907eba4 (Add a domain-realm mapping for EXCHANGE.MIT.EDU) to master
comment:5 Changed 11 years ago by jdreed
- Status changed from committed to proposed
- Fixed in version set to kerberos-config 1.17
Also, Ben says we should remove the ".domain" mappings. For future generations, we could replace them with a comment noting that they are only needed if the host should have a different REALM mapping than other hosts under that domain.