We had a process that worked up until recently that allowed users to authenticate with Okta and grab their Okta application ids; the script logged the user into Okta, then used /login/sessionCookieRedirect to access /api/v1/users/$uid/appLinks (eg. - https://myurl.okta.com/login/sessionCookieRedirect?token=$OneTimeToken&redirectUrl=http://d2l.okta.com/api/v1/users/$uid/appLinks).

Not sure exactly when this started, but recently this started returning 403 forbidden response from Okta. Did something change with Okta login? Is this still supported?