Note: The EDW team cannot provide detailed technical support on using non-Windows machines to connect directly to the EDW. Mac instructions are provided as a courtesy based on feedback from users.
You'll need:
If you're off-campus: Connect to UW VPN first
What this does: Tells your Mac how to authenticate with UW's systems.
sudo nano /etc/krb5.conf
[libdefaults]
default_realm = NETID.WASHINGTON.EDU
ticket_lifetime = 24h
forwardable = true
[realms]
NETID.WASHINGTON.EDU = {
admin_server = _kerberos._tcp.netid.washington.edu
kdc = ezra.netid.washington.edu
kdc = ahsoka.netid.washington.edu
kdc = leia.netid.washington.edu
kdc = kanan.netid.washington.edu
kdc = obiwan.netid.washington.edu
default_domain = NETID.WASHINGTON.EDU
}
[domain_realm]
netid.washington.edu = NETID.WASHINGTON.EDU
.netid.washington.edu = NETID.WASHINGTON.EDU
.s.uw.edu = NETID.WASHINGTON.EDU
4. Save the file: Press Control + O
, Enter
, then Control + X
5. Test your setup - make sure you can reach UW's servers: ping ezra.netid.washington.edu
Ctrl + C
to stop.What this does: Logs you into UW's system and creates a 24-hour access pass.
kinit yournetid@NETID.WASHINGTON.EDU
yournetid
with your actual UW NetIDklist
Your Kerberos authentication is now ready! You can use it with any SQL client that supports Kerberos authentication to connect to EDW.
Before each work session:
kinit yournetid@NETID.WASHINGTON.EDU
in TerminalTo check if your ticket is still valid: klist
To clear your ticket when finished: kdestroy
Error: "KDC reply did not match expectations"
NETID.WASHINGTON.EDU
(all uppercase)Error: "Client not found in Kerberos database"
yournetid@NETID.WASHINGTON.EDU