Firefox and Multiple Kerberos Realms

You will need two profiles: I use my default for my corporate setup, and a new one for development.

(Note:  if you want to keep open a browser, you can use the –no-remote switch so that Firefox doesn’t ignore your pleas to use a different profile, and instead just makes another window that uses the same one.)

firefox -P kfrog  –no-remote &

Go through the steps to create another profile.

In the second window, you need to establish kinit, but running with a different TGT.  You do this with an environment variable:

export KRB5CCNAME=/tmp/krb5ccache

kinit kfrog@TESTREALM.COM

Close and restart firefox.

firefox –no-remote -P ayoung &

RFI: SPEGNO multiple requests

From what we are seeing and what I’ve read, the browser seems to send a JSON request with no Auth info, and then the whole SPEGNO handshake takes place, turning what should be a single request response into (at a minimum) two.  It seems to me that we should be able to avoid that after the initial auth has taken place.

Is there any way to cache SPEGNO information such that successive JSON RPC calls provide the needed information automatically, instead of requiring multiple round trips per request?

Any Fedora people worked with this stuff and know how to optimize it?  Do I need to revert to a Cookie based approach?

Sysadmin’s Req

(If you can’t guess the tune, get off my lawn!)

Are you posting a Sys Admin’s Req
telnet, CUPS, Sendmail,  and BIND
Consider her I worked with  at DEC
She once was an admin of mine

Have her crimp me a crossover cable
telnet, CUPS, Sendmail,  and BIND
Bridging hub and subnet unstable
And then she’ll be an admin of mine

Have her build me a server of web
telnet, CUPS, Sendmail,  and BIND
Without virtualized overhead
And then she’ll be an admin of mine

Have her craft me a Kerberos Key
telnet, CUPS, Sendmail,  and BIND
But not based on code writ at MIT
And then she’ll be an  Admin of mine

Have her write me a recovery plan
telnet, CUPS, Sendmail,  and BIND
With servers unconnected to SAN
And then she’ll be an  admin of mine

streamline development with autoexpect

expect is one of the old UNIX tools that people seem to continually rediscover. It is a hole plugger, linking together other tools to do things that you just can’t do any other way, or at least, not without some serious coding.

I am continually deploying and undeploying IPA Server as part of my development. Installing requires, amongst other things, typing in a password at least four times. I was sick of typing it, and decided to turn to expect.

I’m lazy. I didn’t want to learn another Domain specific language. So, while procrastinating by reading man pages and such, I cam across a tool that made my life much easier.

autoexpect

It is basically a macro recorder for the bash shell.  I ran

autoexpect

ipa-server-install –uninstall

And ran through the install process. When I was done, typed exit, and there was a beautiful expect script all ready for me in script.exp.  renamed it t ipa-uninstall.exp.  Same thing for the install process.

I should rarely, if ever have to type those passwords again.