Timeline for Creating Kerberos credentials cache - Oracle VS Code
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| yesterday | comment | added | grawity_u1686 | "Kinit is the Kerberos command" - which Kerberos implementation though: Oracle's, Java's, MIT, Heimdal? (Windows Kerberos doesn't have a kinit command, so it has to be a third-party implementation.) Where is the actual kinit.exe located? "Is there a file (temporary or otherwise) that would have the current LSASS cache" - No, its entire point is that it is not a file that could be copied; it's managed by a protected process and can only be accessed through the Windows "SSPI" API. (The idea is a bit like ssh-agent but for Kerberos.) | |
| yesterday | comment | added | Ryan F | Honestly just a shot in the dark. Kinit is the Kerberos command, wanted to make sure it was at least generating something I could reference, I'm guessing okinit is what Oracle uses in conjunction with my permissions, as it uses a user@domain field. Is there a file (temporary or otherwise) that would have the current LSASS cache? | |
| yesterday | comment | added | grawity_u1686 |
Are you sure you're supposed to run kinit? It seems like OSMSFT: is telling the client to use the Windows LSASS credential cache – which already did the "kinit" when you logged in to the OS. (Also, if the Oracle tool is 'okinit', then which software package does the other 'kinit' come from?)
|
|
| S 2 days ago | review | First questions | |||
| yesterday | |||||
| S 2 days ago | history | asked | Ryan F | CC BY-SA 4.0 |