I think I'm not going to dig more into it. It looks too much like a rabbit
hole. I was giving a thought to Fediz IDP from Apache. This is basically is
used in CAS.
I'm running out of time to prove this one out, and I'm going to leave it.
thank you for your reply.
On Tuesday, October 30, 2018
Hi Beni,
This has been a very frustrating issue and I have never managed to get it
working correctly.
Interestingly, different cas versions error out but with different errors:
5.1.9 seemed to get past this cxf error but had another problem.
(on the other hand, saml support worked like a charm
Hi Alin,
Have you been able to start CAS server with the generated keys? How did you
manage to generate the required keyStore files and the stscasrealm.jks in
the end?
Please advice. I am dealing with this for over a week and I'm not able to
start CAS server with WS Fed support.
thank you
One correction:
In the cxf sources, it is not
Object[] obj = this.client.invoke(boi, new Object[]{new
DOMSource(writer.getDocument().getDocumentElement())});
Instead it's:
Object obj[] = client.invoke(boi, new DOMSource(writer.getDocument().
getDocumentElement()));
--
- Website:
Brought up cas under debug mode:
- the error happens in
org.apache.cxf.ws.security.trust.AbstractSTSClient.issue() at this line:
Object[] obj = this.client.invoke(boi, new Object[]{new
DOMSource(writer.getDocument().getDocumentElement())});
The error is:
org.apache.cxf.binding.soap.SoapFault:
I got a reply from one of the apereo developers and he did not rule out
the possibility of a bug; advised I should stand up cas in debug mode which
I will work on.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines:
>
> There are some encryption parameters that I have tried, but I am not sure
> what they do. I generated my own jks with the java keytool and placed them
> at the specified locations. Do these settings have anything to do with the
> cxf error above? Maybe, I tried to generate jks files with
Are the log entries before the error normal, is it ok that no service can
be extracted? Any suggestion would be useful at this point. Thank you.
^[[36m2018-04-27 06:34:11,481 DEBUG
[org.apereo.cas.web.support.DefaultArgumentExtractor] - ^[[m
^[[36m2018-04-27 06:34:11,481 DEBUG
So, to summarize, why is cas showing the error "Application not authorized"
when I am trying to go to url https://mycasserver/ws/idp/federation?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions:
>
> But now I have a problem with integrating with a client;
>>
> The client app needs (from the documentation)
- The Federation Service Identifier of the ADFS server, which is located
on the main ADFS properties dialog in the ADFS management application. –
I gave them:
Here is my pom.xml.
On Thursday, April 19, 2018 at 8:03:32 PM UTC-5, AT wrote:
>
> My cas.properties:
>>>
>>
> cas.server.name: https:///xxx
> cas.server.prefix: https:///xxx
>
> cas.serviceRegistry.initFromJson=true
>
> cas.authn.wsfedIdp.idp.realm=urn:org:apereo:cas:ws:idp:realm-CAS
>
>
> My cas.properties:
>>
>
cas.server.name: https:///xxx
cas.server.prefix: https:///xxx
cas.serviceRegistry.initFromJson=true
cas.authn.wsfedIdp.idp.realm=urn:org:apereo:cas:ws:idp:realm-CAS
cas.authn.wsfedIdp.idp.realmName=CAS
cas.authn.wsfedIdp.sts.signingKeystoreFile=
*"Seb" <sre...@cdg33.fr >
> *To: *"CAS Community" <cas-...@apereo.org >
> *Sent: *Wednesday, February 21, 2018 1:53:20 PM
> *Subject: *[cas-user] Re: Problem integrating CAS 5.2.2 with WS
> Federation Identity Provider
>
>
> Hello,
>
> same problem a
Do you see the same problem with 5.2.3-SNAPSHOT?
--Misagh
> From: "Seb" <sre...@cdg33.fr>
> To: "CAS Community" <cas-user@apereo.org>
> Sent: Wednesday, February 21, 2018 1:53:20 PM
> Subject: [cas-user] Re: Problem integrating CAS 5.2.2 with WS Fede
Hello,
same problem as Stephen with 5.2.2,
problem still alive with 5.3.0-RC2.
AT can you share your cas.properties and your pom.xml?
thank you
Le vendredi 2 février 2018 14:00:56 UTC+1, Steffen Fenger a écrit :
>
> Hello,
>
>
> I would like configure a WS Federation Identity Provider
>
> Hello,
>
same problem as Stephen with 5.2.2,
problem still alive with 5.3.0-RC2.
AT can you share your cas.properties and your pom.xml?
thank you
>
>
>
>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines:
>
> So it works under 5.3.0-RC2.
>>
>
Cas autogenerates the encryption/signing keys (still not sure how to add
them to the keystore permanently).
But, at this point I would like to test my idp; usually, from what I
understand, the idp needs to provide:
- The Federation Service Identifier
>
> It compiles using version 5.3.0-RC2.
>
I would really appreciate any guidance you can provide; the error below
shows in the logs so understand I need to generate some additional keys but
there are no instructions or more detailed documentation.
There are some instructions on generating
I am getting the same error in version 5.2.2.
(Btw, I was under the impression the cas-server-
support-ws-sts dependecy is not needed).
Any suggestion would be greatly appreciated.
On Friday, February 2, 2018 at 7:00:56 AM UTC-6, Steffen Fenger wrote:
>
> Hello,
>
>
> I would like configure a
19 matches
Mail list logo
