Mostafa Moradian

@dshinzie I haven't tested it, but it should work. Please create an issue on the fork, so I don't forget to test it.

@dshinzie It now supports all the latest Django versions: https://github.com/grafana/django-saml2-auth/releases/tag/v3.4.0

Hey @heydonovan, You can always match group attribute statements with `GROUPS_MAP` and/or use `NEW_USER_PROFILE.USER_GROUPS`, but I haven't used them. I created a custom user to [teams](https://k6.io/docs/cloud/project-and-team-management/saml-sso/#auto-assigning-your-internal-teams-to-k6-projects)/[project](https://k6.io/docs/cloud/project-and-team-management/saml-sso/#assigning-default-project-s-to-newly-provisioned-users) matching system, which works...

I'll close this due to inactivity. Feel free to re-open it if you still have this issue/question.

Hey @UraizAli, thanks for your contribution. Please consider addressing these two issues: 1. Sign the CLA. 2. Write a test case that includes the unhappy path of not passing `firstname`...

@UraizAli Let me see if I can fix it.

@UraizAli Can you please try again?

@UraizAli Along with the above requested, please fix the linter errors.

@UraizAli https://github.com/grafana/django-saml2-auth/runs/8162584722?check_suite_focus=true 

@UraizAli You still have issues with the linter: https://github.com/grafana/django-saml2-auth/runs/8187930414?check_suite_focus=true Also, I managed to sign the CLA, as shown https://github.com/grafana/django-saml2-auth/pull/73#issuecomment-1196582268. But yours is still unsigned. Also, there is a weird message...