Error in open idm log – HTTP host may not be null

This topic has 0 replies, 1 voice, and was last updated 2 months ago by david.morin.

  • Author
  • #28757

    Hey All,

    I have set up openidm and AM in a platform configuration
    I access the URL of openidm: https://openidmhost:8443/admin
    — i get redirected to AM for logon – I logon with the amadmin account
    — i get redirected back to openidm and get a blank screen

    In the browser developer tools I see an http 500 error and its looking for some url that does not exist https://openidmhost:8443/openidm/info/uiconfig

    I followed this:

    It looks like AM is successfully sending me back to IDM but I am not at all sure where the uiconfig url is coming from

    I do see this error in the openidm log file (snippet)

    INFO: Cannot determine Content-Type of: /
    [62] Nov 17, 2021 6:40:25.439 AM org.forgerock.http.servlet.HttpFrameworkServlet lambda$service$1
    SEVERE: RuntimeException caught – rootId:f557c409-920f-4b30-acdc-212e861b36d2-215
    java.lang.IllegalArgumentException: HTTP host may not be null
    at org.apache.http.util.Args.notNull(
    at org.apache.http.nio.protocol.BasicAsyncRequestProducer.<init>(
    at org.apache.http.nio.client.methods.HttpAsyncMethods$RequestProducerImpl.<init>(
    at org.apache.http.nio.client.methods.HttpAsyncMethods.create(
    at org.forgerock.http.apache.async.AsyncResponseHttpClient.sendAsync(
    at org.forgerock.http.handler.HttpClientHandler.handle(
    at org.forgerock.http.handler.Handlers$UndescribedAsDescribableHandler.handle(
    at org.forgerock.http.filter.TransactionIdOutboundFilter.filter(
    at org.forgerock.http.handler.Handlers$1.handle(
    at org.forgerock.http.filter.Filters$HttpBasicAuthClientFilter.lambda$filter$2(
    at org.forgerock.util.promise.Promises$CompletedPromise.thenAsync(
    at org.forgerock.util.promise.Promises$CompletedPromise.thenAsync(
    at org.forgerock.http.filter.Filters$HttpBasicAuthClientFilter.filter(
    at org.forgerock.http.handler.Handlers$1.handle(
    at org.forgerock.http.oauth2.resolver.TokenIntrospectionAccessTokenResolver.resolve(

    Anyone have any thoughts or ideas?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?