Hi All,
The name-formats used in GSS-API are somewhat different than the
name-formats used in SSPI. So the C# client could not identify the SPN,
as the SPN name of the Java server is not windows compatible. After
providing the SPN name without realm when creating the client credentials
in C#
Hi Hasanthi,
On Tue, Jun 21, 2016 at 3:01 PM, Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:
> Hi Fara/Shazni,
>
> Thanks for the feedback. Here I'm using a sample standalone Java server
> and C# client which communicates through a socket. And I'm using the fully
> qualified name as
Hi Fara/Shazni,
Thanks for the feedback. Here I'm using a sample standalone Java server and
C# client which communicates through a socket. And I'm using the fully
qualified name as you suggested.
As this error comes when validating the server token the the issue should
be with the SPN of java
HI Hasanthi,
I've one question. What's this Java Server? Is it a standalone server you
have custom written or is it a WSO2 server?
When it comes to Kerberos related work for SOAP, we faced a couple of
issues with related to service principal (SPN) name. In that discrepancies
were noticed when
Hi Hasanthi,
Assuming that you are using an AD as the Kerberos Server, Have you
registered a Service Principal for both the C# client and Java Server in
the AD?
You can do this using the setspn.exe. Also, when you registering the SPN
register all possible value that principal can take.
For eg:
Hi I'm implementing Kerberos communication between java (GSSAPI) to
C#(SSPI).
The KDC is an Active Directory. When it comes to Java client vs Java server
and C# client vs C# Server, for both the scenarios this works fine.
When using Java client - server the process happens as below and it works
