401 Unauthorized - Using GSuite as Idp with Gitlab CE 13.0.5

I am trying to integrate GSuite as Idp with Gitlab. I have tried setting up the integration following https://docs.gitlab.com/ee/integration/saml.html#saml-omniauth-provider
Based on the SAML response from GSuite, it appears that GSuite is sending success status, however, GitLab is displaying " Your account has been blocked. Please contact your GitLab administrator if you think this is an error." Please refer below for further details:

GSuite SAML Response (Part of it):
saml2p:Status
<saml2p:StatusCode Value=“urn:oasis:names:tc:SAML:2.0:status:Success” />
</saml2p:Status>

Server Log:
Started POST “/users/auth/saml/callback” for 106.51.82.248 at 2020-06-08 13:44:22 +0000
Processing by OmniauthCallbacksController#saml as HTML
Completed 401 Unauthorized in 35ms (ActiveRecord: 10.5ms | Elasticsearch: 0.0ms | Allocations: 11427)
Started GET “/users/sign_in” for 106.51.82.248 at 2020-06-08 13:44:22 +0000

GitLab CE Version: 13.0.5

It turns out to be false alarm. It all works perfectly the way it should work. During testing I have miss configured omniauth properties. Though the integration with GSuite itself was successful, the configuration was forcing it to go 2FA which was failing and block the user. However, when I looked at the logs, it shows 401 Unauthorized and thought it is the integration problem where Gitlab is not able to parse the SAML response properly.
In the UI it shows “Your account has been blocked. Please contact your GitLab administrator if you think this is an error.” - This message I ignored and thought to believe logs more.
Once I unblocked the user through admin, it all worked in subsequent testing.