Robert Carroll

Finding your Community Users

Discussion created by Robert Carroll on Apr 9, 2019
Latest reply on Apr 29, 2019 by Alexis Page

I was trying to chase down some information for this question, and found that (at least for us) because we use AD/LDAP that the only SAML2 logins were used for SSO to Jive. Which gave me a quick look at our users who have logged into and joined the Canvas Community.

 

Use Cases

  1. Identify faculty looking for more help or collaboration, identify what your faculty need by following your users
  2. Identify students who may have found the wrong space to ask their course/institution specific question, happens all the time in Q & A

 

-- canvas data, requests
SELECT DISTINCT
    user_dim.name
FROM requests
    LEFT JOIN user_dim ON (user_dim.id = requests.user_id)
WHERE
    --PATINDEX('%SAML2/Login?RelayState=%', url) >= 1
    url LIKE '%SAML2/Login?RelayState=%'

-- live events, canvas raw
SELECT DISTINCT
    user_dim.name
FROM live_logged_in
    LEFT JOIN user_dim ON (user_dim.global_canvas_id = live_logged_in.user_id_meta)
WHERE
    --PATINDEX('%SAML2/Login?RelayState=%', redirect_url) >= 1
    redirect_url LIKE '%SAML2/Login?RelayState=%'

-- live events, ims caliper
SELECT DISTINCT
    user_dim.name
FROM ims_logged_in
    LEFT JOIN user_dim ON (user_dim.global_canvas_id = ims_logged_in.actor_entity_id)
WHERE
    --PATINDEX('%SAML2/Login?RelayState=%', object_redirect_url) >= 1
    object_redirect_url LIKE '%SAML2/Login?RelayState=%'

 

Results may also include SSO to cases.canvaslms.com

I suspect other possibilities may be more common as well.

YMMV

Outcomes