Ray,
Thankyou very much for your help. I missed " compile
"org.apereo.cas:cas-server-core-webflow-api:${casServerVersion}" . After
added back, it works now. Thanks again,
Danny
On Wednesday, 24 June 2020 at 23:57:36 UTC+8 rbon wrote:
> Danny,
>
> You may need to include some of these in
We have the same issue. But not on the 6.2 master branch.
On Fri, Jun 26, 2020 at 3:07 PM Amit Poddar wrote:
> Hi,
>
> I am dealing with the same issue, did you get a resolution to this? If
> yes then would you be willing to share the resolution?
>
> Thanks,
> Amit
>
> On Thursday, June 4,
Hi,
I am dealing with the same issue, did you get a resolution to this? If yes
then would you be willing to share the resolution?
Thanks,
Amit
On Thursday, June 4, 2020 at 4:44:50 PM UTC-4, mba...@scad.edu wrote:
>
> Doh, I didn't post the actual error. Here it is:
>
> ERROR
>
I found this link from few years ago discussing this in context of CAS5. It
does not look like what we want is possible, per that link, without
significant customization.
But I am hopeful, that somebody has some creative ideas.
Thanks,
Amit
On Friday, June 26, 2020 at 4:59:03 PM UTC-4, Amit
Hi,
We are trying to utilize the CAS interrupt feature to nag people to
register for multi factor authentication. On the interrupt we are showing
one button to take them to a MFA registration app and continue button to
continue to the original application.
It seems after primary
In Authorization request I need claims for Approve access screen.
Dne pátek 26. června 2020 15:50:55 UTC+2 ste napsal(a):
>
> Ok maybe you need it in response, but not when you request Authorization.
>
> Le ven. 26 juin 2020 à 15:20, Jakub Fridrich > a écrit :
>
>> Yes, for userinfo endpoint I
Ok maybe you need it in response, but not when you request Authorization.
Le ven. 26 juin 2020 à 15:20, Jakub Fridrich <
jakub.fridr...@klikpojisteni.cz> a écrit :
> Yes, for userinfo endpoint I think */cas/oidc/profile*.
>
> For claims, I need this params, generated with XWiki. The above claim
Yes, for userinfo endpoint I think */cas/oidc/profile*.
For claims, I need this params, generated with XWiki. The above claim it I
testing.
*=*{"id_token":{"xwiki_instance_id":null},"userinfo":{
"xwiki_user_accessibility":null,"xwiki_user_displayHiddenDocuments":null,
Ok all look good.
So what is that :
*=*
*{"userinfo":{"sub":null,"iss":null,"openid":null,"profile":null,"name":null,"email":null,"first_name":null,"last_name":null}}*
you don't need it in /cas/oidc/authorize
And when you talk about "In *userinfo* endpoint I getting now" what is your
user info
Hi,
.well-known return this JSON (in attachment)
Dne pátek 26. června 2020 13:50:17 UTC+2 ste napsal(a):
>
> Hi, You see it here : /cas/oidc/.well-known ?
>
> Le ven. 26 juin 2020 à 09:07, Jakub Fridrich > a écrit :
>
>> Thanks, but attributes not showing still..
>>
>> My service now looks
Hi, You see it here : /cas/oidc/.well-known ?
Le ven. 26 juin 2020 à 09:07, Jakub Fridrich <
jakub.fridr...@klikpojisteni.cz> a écrit :
> Thanks, but attributes not showing still..
>
> My service now looks like:
> {
> "@class" : "org.apereo.cas.services.OidcRegisteredService",
> "clientId":
I don't know the purpose of your claim parameter but here's the kind of url
generated by our oidc client:
https://xxx/cas/oidc/authorize?client_id=
_uri=https%3A%2F%2Fyyy%2Fsilent-renew-oidc.html
_type=id_token%20token
=openid%20profile%20email
=vvv
=www
=none
Le vendredi 26 juin
Thanks, but attributes not showing still..
My service now looks like:
{
"@class" : "org.apereo.cas.services.OidcRegisteredService",
"clientId": "",
"clientSecret": "XX-X",
"serviceId": "^https://xwikl.XXX*;,
"name": "",
"id": 20,
"scopes" : [
13 matches
Mail list logo
