Unable to create user in apigee onprem

Hi,

We have two data centers for In-prod org.. I am able to login to the apigee edge bit when i tried to on board new user getting error bad request. From edge UI logs i found below message

utils.GatewayErrorResponseException: 400 https://mgmt-in-api.experian.com:443/v1/users null null at utils.WsHelper.logAndBuildExceptionForGatewayErrorResponse(WsHelper.java:113) at utils.Play2Utils$HandleError.apply(Play2Utils.java:41) at utils.Play2Utils$HandleError.apply(Play2Utils.java:29) at play.core.j.FPromiseHelper$anonfun$map$1.apply(FPromiseHelper.scala:103) at scala.util.Success$anonfun$map$1.apply(Try.scala:236) at scala.util.Try$.apply(Try.scala:191) at scala.util.Success.map(Try.scala:236) at scala.concurrent.Future$anonfun$map$1.apply(Future.scala:235) at scala.concurrent.Future$anonfun$map$1.apply(Future.scala:235) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) at play.core.j.HttpExecutionContext$anon$2.run(HttpExecutionContext.scala:40) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

Thanks,

M Kumari.

Solved Solved
0 11 332
1 ACCEPTED SOLUTION

Not applicable

Call to

https://mgmt-in-api.experian.com:443/v1/users

Is throwing error. Can you try creating user using management api call?

What is the status of your management and LDAP components?

View solution in original post

11 REPLIES 11

Not applicable

Call to

https://mgmt-in-api.experian.com:443/v1/users

Is throwing error. Can you try creating user using management api call?

What is the status of your management and LDAP components?

Hi Priyadarshi,

Thank you so much for your support. Amazing. Now i am able to create users thru MS API calls

By using https://mgmt-in-api.experian.com:443/v1/users instead of Localhost:8443.

Earlier i am unable to create users even thruManagement api calls.

But still we are unable to create users thru edge ui.All components status up only we did restrt the components also but no use same error we are getting.

Thanks,

M Kumari.

why don't you uninstall and reinstall edge ui. This will not have any negative impact on your traffic.

I am scared if it causes to other issues. Could you please mention the proper steps to do?

This command is enough right or we need to do any other commands. Before uninstall we need to take any logs

/opt/apigee/apigee-service/bin/apigee-service apigee-service uninstall

edge-ui uninstall instead of apigee-service

And ensure your config file is available with you.

Actualyy we are followed below two documents to setup apigee-sso

https://docs.apigee.com/private-cloud/v4.19.06/install-and-configure-edge-sso

https://docs.apigee.com/private-cloud/v4.19.06/install-and-configure-edge-sso

We setup everything correctly but don't know why we unabe to create users thru edge ui.

Thanks,

M Kumari.

I have created one user through management api calls. So what i did i deleted that user in edge ui and try to create again through edge ui suprisingly i am able to create user for deleting user. But still unable to create any other users except which i created through management api call.

I didnt get the logic behind it

When you create user through management api it creates a global user. Once you created then delete only doesn't remove the global user info from LDAP and when you add using UI it works. But when you are creating through UI it is not able to create a global user in your case.

Can you try the same once desabling the SSO. If that works then your SSO configuration is missing something.

Sorry i am not aware how to disable the sso. could you please provide the steps.

these are the steps we need to follow right

https://docs.apigee.com/private-cloud/v4.18.05/disable-saml

Does it affect anything. After testing can we again enable it without fail.