The new LMS hostname answers. Students sign in. The IdP still has last year's ACS URL in the SAML application. On the next IdP-initiated login, or on a bookmark that still posts to the old name, the assertion goes where the IdP is configured to send it.

A DNS A record and a valid certificate on the old name tell you the name still answers. The SAML recipient is the ACS URL the IdP will POST to.

Build an exact-match inventory of ACS and Entity ID values the IdP trusts, against the production destinations you still own.

What the LMS publishes as ACS

On Moodle™ with Catalyst auth_saml2, the Okta mapping table in the plugin README (MOODLE_500_STABLE) is:

Okta nameSane nameValue
Single sign on URLACS URLhttps://example.com/auth/saml2/sp/saml2-acs.php/example.com
Audience URIEntity IDhttps://example.com/auth/saml2/sp/metadata.php
Single Logout URLSingle Logout URLhttps://example.com/auth/saml2/sp/saml2-logout.php/example.com

example.com here is $CFG->wwwroot without the scheme. The ACS path includes that host a second time after saml2-acs.php/. Change wwwroot and the ACS string changes. The README's Bitnami gotcha is the same fact: $CFG->wwwroot must be a static value in config.php. Certificates live in $CFG->dataroot/saml2. The stand-alone test page is /auth/saml2/test.php; it echoes SAML attributes without rendering a Moodle™ page.

On Canvas, Instructure's Okta walkthrough sets:

  • Single sign-on URL (ACS): https://YOURDOMAIN.instructure.com/login/saml
  • Audience URI (SP Entity ID): http://YOURDOMAIN.instructure.com/saml2 — HTTP, not HTTPS
  • Extra requestable SSO URLs: https://YOURDOMAIN.beta.instructure.com/login/saml (index 2), https://YOURDOMAIN.test.instructure.com/login/saml (index 3), and for a vanity host https://YOURVANITYURL/login/saml (index 4)

Canvas metadata is at https://YOURDOMAIN.instructure.com/saml2. The Authentication Providers API documents saml_entity_id as defaulting to <host>/saml2 when unset.

Those strings are the intended production set. Anything else in the IdP is a delta.

Why leftover ACS URLs survive a migration

A hostname cutover updates the LMS wwwroot or the Canvas vanity domain. The IdP application is a second object. Admins add the new ACS so the new site works, and leave the old one because a rollback might need it, because Okta already had "Allow this app to request other SSO URLs" checked, or because a beta/test/vanity URL was added once and never retired.

The old name can still have DNS and TLS. That is enough for a browser to complete a POST. It is not evidence that the host is the current SP, that it still has the matching certificate in $CFG->dataroot/saml2, or that Destination in the AuthnRequest matches wwwroot. Catalyst documents Destination mismatches (including port) as login failures. A leftover ACS that still accepts the assertion is the other side of that: the IdP is willing to POST there.

An extra trusted ACS is leftover trust. Classify it. Owner, environment (prod / beta / test / vanity / unknown), and the date you expect it to leave the IdP.

The inventory

Export the SAML application's ACS list from the IdP you administer. Okta: the SAML settings for that app, including Other Requestable SSO URLs. Entra: Basic SAML Configuration Identifier and Reply URL. The LMS side is the SP metadata you already publish.

On a Moodle™ you own:

# SP metadata (Entity ID + ACS live in this document)
curl -sS -D - -o /tmp/sp-metadata.xml \
  "$WWWROOT/auth/saml2/sp/metadata.php"

ACS will be $WWWROOT/auth/saml2/sp/saml2-acs.php/<host>. Confirm wwwroot is the host you think it is.

On Canvas you administer:

AUTH="Authorization: Bearer $CANVAS_TOKEN"

curl -sS -D - -o /tmp/auth-providers.json \
  -H "$AUTH" \
  "$CANVAS/api/v1/accounts/self/authentication_providers"

Read saml_entity_id, log_in_url, log_out_url. Fetch https://YOURDOMAIN.instructure.com/saml2 for the AssertionConsumerService locations in the XML.

Build a table. Exact string match. Scheme, host, port, and path all count. Canvas Entity ID is http://, ACS is https://.

ACS or Entity ID stringSourceEnvironmentOwnerIn approved setRetirement date
IdP app
LMS metadata

Approved set is the current production ACS plus the beta/test/vanity URLs you still operate. Everything else is a delta.

How to classify a delta

  • Current production. Keep. This is the row the monitor is anchored on.
  • Documented non-prod. Canvas beta and test, a Moodle™ staging wwwroot you still own. Keep with an owner and a review date.
  • Retired hostname you still own. Remove from the IdP after the LMS on that name is decommissioned, or keep it only with a dated rollback window.
  • Unknown host. Do not POST a test assertion to it. Do not collect learner assertions. Look up ownership in your own DNS and certificate inventory. If it is not yours, treat it as an incident for the IdP admin: an ACS the application will use, on a host you do not operate.

A successful curl -I on the old hostname is a liveness check for DNS and TLS. Put that in a different column from "this string is in the IdP ACS list". The monitor fires on the string delta, then you use liveness to decide how urgent the leftover is.

On a Moodle™ test instance you own, /auth/saml2/test.php is the right place to confirm the current ACS still consumes an assertion. Use it on the current wwwroot. Skip retired hosts you do not own.

Wildcards and default reply URLs

Read the IdP's actual wildcard and default-reply behaviour before you write a regex. Some IdPs treat a default RelayState or a default reply URL as a destination when the request omits one. An exact-match list still works: include that default in the approved set, or the first unsolicited IdP-initiated login will look like a delta.

Port and trailing slash are part of the string. https://lms.example.org/auth/saml2/sp/saml2-acs.php/lms.example.org and the same URL on :443 explicitly are different ACS values if the IdP stored both.

What this monitor is

This is IdP trust after a hostname change. It answers one question: is every ACS and Entity ID string this SAML application will send an assertion to, in the approved set for hosts you still operate.

It is a different check from leftover authenticated sessions after IdP logout, from login 302 header loss, and from a log heartbeat.

Disclosure: I work on GuardLMS, a product of Ldesign Media. The ACS paths, Entity IDs, and extra SSO URL indexes above are from the Catalyst auth_saml2 README (MOODLE_500_STABLE), Instructure's Okta configuration walkthrough, and the Canvas Authentication Providers API.