Please check the serviceRegistry configuration for you application. If the 
url of the application you have integrated with cas is not matched with 
that of defined in service registry then it'll give the the errors. 

As a sample app you can use the following snippet

{
  "@class": "org.apereo.cas.services.RegexRegisteredService",
  "serviceId": "^(http|https|imaps)://.*",
  "name": "HTTPS and IMAPS",
  "id": 10000001,
  "description": "This service definition authorizes all application urls 
that support HTTPS and IMAPS protocols.",
  "proxyPolicy":
  {
    "@class": "org.apereo.cas.services.RefuseRegisteredServiceProxyPolicy"
  },
  "evaluationOrder": 10000,
  "usernameAttributeProvider":
  {
    "@class": 
"org.apereo.cas.services.DefaultRegisteredServiceUsernameProvider",
    "canonicalizationMode": "NONE",
    "encryptUsername": false
  },
  "logoutType" : "BACK_CHANNEL",
  "attributeReleasePolicy":
  {
    "@class": "org.apereo.cas.services.ReturnAllowedAttributeReleasePolicy",
    "principalAttributesRepository":
    {
      "@class": 
"org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository",
      "expiration": 2,
      "timeUnit": "HOURS"
    },
    "authorizedToReleaseCredentialPassword": false,
    "authorizedToReleaseProxyGrantingTicket": false,
    "excludeDefaultAttributes": false
  },
  "multifactorPolicy":
  {
    "@class": 
"org.apereo.cas.services.DefaultRegisteredServiceMultifactorPolicy",
    "failureMode": "CLOSED",
    "bypassEnabled": false
  },
  "accessStrategy":
  {
    "@class": 
"org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
    "enabled": true,
    "ssoEnabled": true,
    "requireAllAttributes": true,
    "caseInsensitive": false
  }
}

Where *serviceId *is the regex which will define the url pattern for the 
application trying to register with cas. In the above snippet it'll allow 
all the apps to use cas.



On Tuesday, June 6, 2017 at 7:36:47 PM UTC+5:30, Ashley Mort wrote:
>
> I have been using https://github.com/apereo/cas-overlay-template which 
> used CAS 5.0.6 which worked great for me.  However when I pull the update 
> from 5/31/17 which bumps the CAS version to 5.1.0, I get the following new 
> problems:
>
> 1- "Application Not Authorized to Use CAS" for all my apps
> 2- "You did not say the magic word!" error when I try to access 
> /cas/status/dashboard
>
> Can anyone please advise?  I did not see either of these issuse with the 
> cas-overlay-template that used CAS 5.0.6 but the change in the pom.xml to 
> use 5.1.0 results in these above issues.
>
> Thank yoU!
>

-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/0a3cf202-47b6-4be2-a38a-7e75b3618db8%40apereo.org.

Reply via email to