Maybe this is what is causing your config not to work with us, we are using
version 6.1.0-RC4.
On Sun, Nov 17, 2019 at 2:33 PM Abdelrahman Halawa
wrote:
> CAS v5.3.x
>
>
>
>
> On Sun, 17 Nov 2019 at 09:44, mohamed gamal
> wrote:
>
>> Mr Abdelrahman, thanks for your support.
>> which version
CAS v5.3.x
On Sun, 17 Nov 2019 at 09:44, mohamed gamal
wrote:
> Mr Abdelrahman, thanks for your support.
> which version are you using ?
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> -
Mr Abdelrahman, thanks for your support.
which version are you using ?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are
Hi Mohammed,
below is my JSON file, you are free to use it and try. but you must
configure the SharePoint to use UPN and mail claims as the JSON shows.
Hint: It is a must to use the *realmcas *certificate as the signing
certificate for SharePoint config.
{
"@class" :
Unfortunatly Mr Abdelrahman,
>
> we are still facing the same error
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are
Hi Mohammed,
Everything looks good except you need to set the token type in JSON file to
be SAMLV1.1.
SharePoint supports SAMLV1.1 only and the default in CAS is SAMLv2.
Change your JSON file as below and try again
..
"evaluationOrder" : 2,
"tokenType" : "
Dear Abdelrahman,
Below you can find the configuration and ther service json.
Thanks for your support
cas.authn.wsfedIdp.idp.realm=urn:org:apereo:cas:ws:idp:realm-CAS
cas.authn.wsfedIdp.idp.realmName=CAS
cas.authn.wsfedIdp.sts.subjectNameIdFormat=unspecified
Dear Abdelrahman,
Below you can find the configuration and ther service json.
Thanks for your support
cas.authn.wsfedIdp.idp.realm=urn:org:apereo:cas:ws:idp:realm-CAS
cas.authn.wsfedIdp.idp.realmName=CAS
cas.authn.wsfedIdp.sts.subjectNameIdFormat=unspecified
Hi Mohammed,
Could you share your WS-Fed configuration with the CAS and JSON file of the
service as well may I help you.
On Tue, Nov 12, 2019 at 7:39 AM mohamed gamal
wrote:
> Hello Steve,
> Thanks for your support.
> but now I am getting this error
> DEBUG
Hello Steve,
Thanks for your support.
but now I am getting this error
DEBUG [org.apereo.cas.support.realm.UriRealmParser] -
│
│2019-11-11 13:22:51,868 WARN
Hello everyone,
I am trying to integrate cas with a share point application using WS-FED I
added the service file and the application connects normally to cas. the
app redirects the user to cas for authentication, the user is authenticated
by cas and I can see in logs that the user is
FYI --- this post is old and resolved via great assistance from David (fThe
New School).
The filters are holding back emails sent to the list.
On Mon, May 14, 2018 at 10:43 AM, Jann Malenkoff
wrote:
> Hello:
>
> I have been tacking with the JSON enabling of
Hello:
I have been tacking with the JSON enabling of
'http://localhost:8080/cas-management' over the weekend.
Wondering if I can change approach and tackle this by entering SQL to the
DB tables (screenshot attached).
Would there be a resource with instruction on which tables to update?
Apologies if this is a double post -- my earlier one may not have gone
through.
I have been battling via the JASON service registry over the weekend --
raising the white flag and planning the JPA route.
Attempting to access:
http%3A%2F%2Flocalhost%3A8080%2Fcas-management%2Fmanage.html
"The
Application Not Authorized to Use CAS The application you attempted to
authenticate to is not authorized to use CAS.
I keep getting this error. CAS-MANAGEMENT i am not able to run. Have any
other solution to get rid of this error.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom:
15 matches
Mail list logo