<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/15/13 6:10 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote
cite="mid:BA63CEAE152A7742B854C678D9491383BF94944E@CIO-KRC-D1MBX03.osuad.osu.edu"
type="cite">
<blockquote type="cite" style="color: #000000;">
<pre wrap="">Should I enable the JAAS handler, then configure the appropriate JAAS
<span class="moz-txt-citetags">></span>setting, e.g. <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:jmenchaca@verticalresponse.com">"jmenchaca@verticalresponse.com"</a>=password?
</pre>
</blockquote>
<pre wrap="">That is not a valid JAAS approach.
</pre>
</blockquote>
I was wondering, when I was sleuthing through JAAS documentation, I
found this "users.properties file". Could I use that?<br>
<br>
<font face="Courier New, Courier, monospace">ShibUserPassAuth {<br>
users.properties file<br>
<a class="moz-txt-link-rfc2396E"
href="mailto:testuser@somecompany.com">"testuser@somecompany.com"</a>=password<br>
};</font><br>
<br>
This is how I was trying to configure that component. I am trying
to look for the path of least resistance. I thought of doing the
Apache front-end (not for authentication) because I wanted an easy
way to bind to port 443. From reading material, there were
considerations (needed configurations) specific to Tomcat +
Shibboleth + Apache. This was better documented in 1.x than it is
in 2.x. Seeing that, I avoided Apache for the initial
Proof-of-Concept, and was hoping this JAAS configuration might
work... <br>
</body>
</html>