@lightalakanzam Not with standard fusionauth, because the hosted login pages don't know that the login has occurred.
You could perhaps set a cookie on login with the login API and then look for that cookie in an http proxy in front of FusionAuth, and deny access to the login pages at that time.
Or, you could, if you are only using the login API, set up the theme to have a blank login page.
and/or detect that the user was an IdP managed user?
In the reconcile lambda from the IdP (here's the docs for the OIDC lambda), you can set whatever data you want on the user.data field, so you could set user.data.idpUser = true. Then you can access that value from the self edit page freemarker template and decide to show or hide the password field.
I get that this isn't as straightforward as it would be if the original feature request was implemented 🙂 . But I think there's a path forward here that doesn't wait on that.
Elasticsearch access is not available for FusionAuth cloud deployments.
I would recommend running FusionAuth locally, which should display similar results as your cloud deployment for how the user and the entities are mapped.
Users can be deactivated and reactivated using the User API. The following FusionAuth documentation outlines deactivation (or soft-delete) and reactivation:
Delete A User (soft-delete them, don't hard delete them)
