I have successfully configured CAS to act as an OpenId Connect Provider
(OP). While investigating a timeout with ownCloud (2.9.x) Desktop client
which uses Dynamic Client Registration, it seems, according to the client
log, that the "Required" field "client_secret_expires_at" (according to
atching strategy used in theservice definition is
correct and does in fact match the client [http://127.0. 0.1:40709]>
On Thursday, November 11, 2021 at 8:45:40 AM UTC-5 G Lalonde wrote:
> This latest release (RC2) has fixed the issue with the missing
> "client_secret_expires_at"
This latest release (RC2) has fixed the issue with the missing
"client_secret_expires_at" field but unfortunately the JSON service
definition created by the client registration (i.e. ownCloud Desktop
client) is created with a serviceId of "http://127.0.0.1; but the
redirected_uri always
16 PM UTC-5 Ray Bon wrote:
> In the service definition you can use a regex.
> Try something like http://127.0.0.1.*
>
> Ray
>
> On Tue, 2021-11-23 at 05:40 -0800, G Lalonde wrote:
>
> Notice: This message was sent from outside the University of Victoria
> email syste
I've started trying out version 7.0.0-SNAPSHOT in the past few days. My
previous "production" build was done with version 6.5.2 - hence I've just
got introduced to the cas-initializr build approach.
I've made different builds with varying list of dependencies but the latest
one is below:
Thank you Misagh.
On Friday, November 18, 2022 at 11:02:03 AM UTC-5 Misagh Moayyed wrote:
> > I have two questions:
> >
> > 1) I'm unclear on the impact of including the "core" and "webapp"
> dependencies i.e. to I need to the specify them?
>
> No. They are implicitly included.
>
> > 2) In
I'm encountering the following error returned on the display
{"error":"invalid_request","error_description":"Unsupported prompt
parameter value"}
which I suspect is related to the "prompt=select_account" element for the
following oidcAuthorize call
