If I do not try and use the lc.login() method and instead try to pull from
the /etc/krb5.keytab file then I get the below error:
10988 [http-8080-Processor25] DEBUG
org.apache.ws.security.kerberos.GSSAuthorizor - Setting Realm/KDC/Config to
BWOO.COM/10.0.78.20//tmp/jaas.conf
10988 [http-8080-Proc
Fredrik Tolf wrote:
I checked the code you mention, but as far as I am able to tell, the
first one only runs in case no log specifications have been loaded
(if(log_control.log_nentries == 0)). Therefore, I cannot see that being
the cause for double messages. It also doesn't explain why the ordina
Tried that already too and received:
GSSException: GSSException: No valid credentials provided (Mechanism level:
Failed to find any Kerberos Key)
If I don't setup the Kerberos stuff before calling that GSSCredentials I get
that error (See code below).
GSSManager manager = GSSManager.getInstanc
On 11/30/05, Douglas E. Engert <[EMAIL PROTECTED]> wrote:
>
>
>
> So you are using GSSAPI, and passing the GSSAPI tokens via soap betwen the
> clint and server. And the server accepts the authentication.
Prior to the server even looking at the packet from the client, it needs to
contact the kerbe
The server is running on the same machine as the client.
I have one development box running.
Server is running as a tomcat servlet (Utilizing Apache's Axis SOAP
interface). The client contacts the kerberos server, grabs the appropriate
ticket and uses the GSS API to generate a ticket. The client
Laurence Brockman wrote:
Tried that already too and received:
GSSException: GSSException: No valid credentials provided (Mechanism level:
Failed to find any Kerberos Key)
Then you have to get the key into the keytab. This is the way a server works,
It does not try and get a ticket.
Figur
