You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a local (on-premise) platform UI (PUI) deployment, similar to IDCloud. Is there a way to export and import config ( AM and IDM ) using the tool for an on-premise/local installation OR this tool is specifically for IDCloud only.
I don't think the service account approach works for local installation and we could not find a way to create a service account for on-premise installation.
Regards,
Debasis
The text was updated successfully, but these errors were encountered:
I have the same question ;), in my case is a Forgerock Identity Platform (7.5) deployed on EKS and I can't find a way to create the required service account. I have searching on Forgerock community about service accounts and It seems that is a feature only for advance identity cloud.
Any work arround? Regards!
The fr-config-manager tool is specifically for Identity Cloud. A lot of configuration will be the same or similar, but the ways of accessing it via service accounts, plus ESVs etc, are specific to cloud.
The frodo project is a more generic tool for managing ForgeRock platform config - that would be the best starting point for managing non-cloud environments.
The fr-config-manager tool is specifically for Identity Cloud. A lot of configuration will be the same or similar, but the ways of accessing it via service accounts, plus ESVs etc, are specific to cloud.
The frodo project is a more generic tool for managing ForgeRock platform config - that would be the best starting point for managing non-cloud environments.
Hi,
We have a local (on-premise) platform UI (PUI) deployment, similar to IDCloud. Is there a way to export and import config ( AM and IDM ) using the tool for an on-premise/local installation OR this tool is specifically for IDCloud only.
I don't think the service account approach works for local installation and we could not find a way to create a service account for on-premise installation.
Regards,
Debasis
The text was updated successfully, but these errors were encountered: