Home

Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: OSP error

  1. #1
    Join Date
    Dec 2018
    Posts
    21

    OSP error

    Detail error in "osp-idm.2019-03-27.log"


    Preamble: [OSP]
    Priority Level: WARNING
    Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest() [474] thread=http-nio-8080-exec-2
    Time: 2019-03-27T10:18:36.522-0300
    Log Data: InternalError

    Preamble: [OSP]
    Priority Level: SEVERE
    Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281] thread=http-nio-8080-exec-2
    Time: 2019-03-27T10:18:36.788-0300
    Log Data: Code: internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    Text: Unrecognized interface. Invalid Host Header Name or Request URL Domain Name.

    Preamble: [OSP]
    Priority Level: WARNING
    Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest() [474] thread=http-nio-8080-exec-5
    Time: 2019-03-27T10:18:46.710-0300
    Log Data: InternalError

    Preamble: [OSP]
    Priority Level: SEVERE
    Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281] thread=http-nio-8080-exec-5
    Time: 2019-03-27T10:18:46.710-0300
    Log Data: Code: internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    Text: Unrecognized interface. Invalid Host Header Name or Request URL Domain Name.

    Preamble: [OSP]
    Priority Level: WARNING
    Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest() [474] thread=http-nio-8080-exec-7
    Time: 2019-03-27T10:19:55.106-0300
    Log Data: InternalError

    Preamble: [OSP]
    Priority Level: SEVERE
    Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281] thread=http-nio-8080-exec-7
    Time: 2019-03-27T10:19:55.106-0300
    Log Data: Code: internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    Text: Unrecognized interface. Invalid Host Header Name or Request URL Domain Name.

    Preamble: [OIDP]
    Priority Level: SEVERE
    Java: internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError() [582] thread=https-openssl-nio-8443-exec-10
    Time: 2019-03-27T10:20:06.264-0300
    Log Data: Code: internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>() [183]
    Text: Client-supplied redirect URI is not registered: http://w16qavidgsrv01.ad.gi.cl:8080/oauth.html

    Preamble: [OIDP]
    Priority Level: SEVERE
    Java: internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError() [582] thread=https-openssl-nio-8443-exec-9
    Time: 2019-03-27T10:21:43.829-0300
    Log Data: Code: internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>() [183]
    Text: Supplied client identifier is invalid.

    Preamble: [OIDP]
    Priority Level: SEVERE
    Java: internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError() [582] thread=https-openssl-nio-8443-exec-10
    Time: 2019-03-27T10:23:51.538-0300
    Log Data: Code: internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>() [183]
    Text: Supplied client identifier is invalid.

    Detail error (only one) in catalina.2019-03-26.log:



    [SEVERE] 2019-03-26 18:44:36 com.netiq.iac.server.j2ee.ArcServerInitListener loadBaseData - [IG-SERVER] Encountered unexpected error: Encountered unexpected exception


    Server install details:
    APP Server: IG 3.5 + Script install ("IDGov35-Core-Helper-IDGov.ps1") + Certificate SHA256withRSA
    DB Server: PostgreSQL
    RPT Server: PostgreSQL + Script install ("IDGov35-Core-Helper-Base.ps1") + Certificate SHA256withRSA

  2. #2
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: OSP error

    On 3/27/2019 10:04 AM, sosix wrote:
    >
    > Detail error in "osp-idm.2019-03-27.log"
    >
    >
    >> Preamble: [OSP]
    >> Priority Level: WARNING
    >> Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest()
    >> [474] thread=http-nio-8080-exec-2
    >> Time: 2019-03-27T10:18:36.522-0300
    >> Log Data: InternalError
    >>
    >> Preamble: [OSP]
    >> Priority Level: SEVERE
    >> Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281]
    >> thread=http-nio-8080-exec-2
    >> Time: 2019-03-27T10:18:36.788-0300
    >> Log Data: Code:
    >> internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    >> Text: Unrecognized interface. Invalid Host Header Name or Request URL
    >> Domain Name.
    >>
    >> Preamble: [OSP]
    >> Priority Level: WARNING
    >> Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest()
    >> [474] thread=http-nio-8080-exec-5
    >> Time: 2019-03-27T10:18:46.710-0300
    >> Log Data: InternalError
    >>
    >> Preamble: [OSP]
    >> Priority Level: SEVERE
    >> Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281]
    >> thread=http-nio-8080-exec-5
    >> Time: 2019-03-27T10:18:46.710-0300
    >> Log Data: Code:
    >> internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    >> Text: Unrecognized interface. Invalid Host Header Name or Request URL
    >> Domain Name.
    >>
    >> Preamble: [OSP]
    >> Priority Level: WARNING
    >> Java: internal.osp.framework.servlet.OSPServlet.auditFai ledRequest()
    >> [474] thread=http-nio-8080-exec-7
    >> Time: 2019-03-27T10:19:55.106-0300
    >> Log Data: InternalError
    >>
    >> Preamble: [OSP]
    >> Priority Level: SEVERE
    >> Java: internal.osp.framework.servlet.OSPServlet.errorRes ponse() [281]
    >> thread=http-nio-8080-exec-7
    >> Time: 2019-03-27T10:19:55.106-0300
    >> Log Data: Code:
    >> internal.osp.framework.handler.TenantRequestHandle r.<init>() [70]
    >> Text: Unrecognized interface. Invalid Host Header Name or Request URL
    >> Domain Name.
    >>
    >> Preamble: [OIDP]
    >> Priority Level: SEVERE
    >> Java:
    >> internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError()
    >> [582] thread=https-openssl-nio-8443-exec-10
    >> Time: 2019-03-27T10:20:06.264-0300
    >> Log Data: Code:
    >> internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>()
    >> [183]
    >> Text: Client-supplied redirect URI is not registered:
    >> http://w16qavidgsrv01.ad.gi.cl:8080/oauth.html
    >>
    >> Preamble: [OIDP]
    >> Priority Level: SEVERE
    >> Java:
    >> internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError()
    >> [582] thread=https-openssl-nio-8443-exec-9
    >> Time: 2019-03-27T10:21:43.829-0300
    >> Log Data: Code:
    >> internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>()
    >> [183]
    >> Text: Supplied client identifier is invalid.
    >>
    >> Preamble: [OIDP]
    >> Priority Level: SEVERE
    >> Java:
    >> internal.osp.oidp.service.oauth2.handler.RequestHa ndler.respondWithPageError()
    >> [582] thread=https-openssl-nio-8443-exec-10
    >> Time: 2019-03-27T10:23:51.538-0300
    >> Log Data: Code:
    >> internal.osp.oidp.service.oauth2.handler.HandlerEx ception.<init>()
    >> [183]
    >> Text: Supplied client identifier is invalid.

    >
    >
    > Detail error (only one) in catalina.2019-03-26.log:
    >
    >
    >
    >> [SEVERE] 2019-03-26 18:44:36
    >> com.netiq.iac.server.j2ee.ArcServerInitListener loadBaseData -
    >> [IG-SERVER] Encountered unexpected error: Encountered unexpected
    >> exception



    OSP is super duper picky about the URL in the browser bar, matching the
    value in the config. It is annoying, but apparently part of teh
    standard, so operating correctly.

    In the ism-configuration.properties (in your Tomcat/conf dir) what value
    do you have for the osp url? I forget the property name, but they should
    all be basically the same in the file.

    Is it exactly:
    http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?

    > Server install details:
    > APP Server: IG 3.5 + Script install ("IDGov35-Core-Helper-IDGov.ps1") +
    > Certificate SHA256withRSA
    > DB Server: PostgreSQL
    > RPT Server: PostgreSQL + Script install ("IDGov35-Core-Helper-Base.ps1")
    > + Certificate SHA256withRSA
    >
    >



  3. #3
    Join Date
    Dec 2018
    Posts
    21

    Re: OSP error

    OSP is super duper picky about the URL in the browser bar, matching the
    value in the config. It is annoying, but apparently part of teh
    standard, so operating correctly.

    In the ism-configuration.properties (in your Tomcat/conf dir) what value
    do you have for the osp url? I forget the property name, but they should
    all be basically the same in the file.

    Is it exactly:
    http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?

    Is not the same...

    Detail ism.configuration.properties:

    com.netiq.idm.osp.url.host = https://w16qavidgsrv01.ad.gi.cl:8443

  4. #4
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: OSP error

    On 3/27/2019 10:44 AM, sosix wrote:
    >
    >> OSP is super duper picky about the URL in the browser bar, matching the
    >> value in the config. It is annoying, but apparently part of teh
    >> standard, so operating correctly.
    >>
    >> In the ism-configuration.properties (in your Tomcat/conf dir) what value
    >> do you have for the osp url? I forget the property name, but they should
    >> all be basically the same in the file.
    >>
    >> Is it exactly:
    >> http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?

    >
    >
    > Is not the same...
    >
    > Detail ism.configuration.properties:
    >
    >>
    >> com.netiq.idm.osp.url.host = https://w16qavidgsrv01.ad.gi.cl:8443


    So, one of these things is not like the other, one of these things,
    doesn't belong, can you tell me which one of these is not like the
    other, before I finish this song? (Hat tip to Sesame Street).

    So... You MUST access services authenticated by OSP via the configured
    URL. Period.

    So, have you tried the proper URL? Does that work?



  5. #5
    stevewdj is offline Micro Focus Employee - Ultra Contributor
    Join Date
    May 2016
    Posts
    723

    Re: OSP error

    On 3/27/19 10:48 AM, Geoffrey Carman wrote:
    > On 3/27/2019 10:44 AM, sosix wrote:
    >>
    >>> OSP is super duper picky about the URL in the browser bar, matching the
    >>> value in the config. It is annoying, but apparently part of teh
    >>> standard, so operating correctly.
    >>>
    >>> In the ism-configuration.properties (in your Tomcat/conf dir) what value
    >>> do you have for the osp url? I forget the property name, but they should
    >>> all be basically the same in the file.
    >>>
    >>> Is it exactly:
    >>> http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?

    >>
    >>
    >> Is not the same...
    >>
    >> Detail ism.configuration.properties:
    >>
    >>>
    >>> com.netiq.idm.osp.url.host = https://w16qavidgsrv01.ad.gi.cl:8443

    >
    > So, one of these things is not like the other, one of these things,
    > doesn't belong, can you tell me which one of these is not like the
    > other, before I finish this song?* (Hat tip to Sesame Street).
    >
    > So... You MUST access services authenticated by OSP via the configured
    > URL. Period.
    >
    > So, have you tried the proper URL?* Does that work?
    >
    >

    Greetings,
    If you have switched from http to https you have to update the
    redirect and server information in both configutil and configupdate. ID
    Gov has to know and so does OSP.

    --
    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    Micro Focus

  6. #6
    Join Date
    Dec 2018
    Posts
    21

    Re: OSP error

    Quote Originally Posted by stevewdj View Post
    On 3/27/19 10:48 AM, Geoffrey Carman wrote:
    > On 3/27/2019 10:44 AM, sosix wrote:
    >>
    >>> OSP is super duper picky about the URL in the browser bar, matching the
    >>> value in the config. It is annoying, but apparently part of teh
    >>> standard, so operating correctly.
    >>>
    >>> In the ism-configuration.properties (in your Tomcat/conf dir) what value
    >>> do you have for the osp url? I forget the property name, but they should
    >>> all be basically the same in the file.
    >>>
    >>> Is it exactly:
    >>> http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?

    >>
    >>
    >> Is not the same...
    >>
    >> Detail ism.configuration.properties:
    >>
    >>>
    >>> com.netiq.idm.osp.url.host = https://w16qavidgsrv01.ad.gi.cl:8443

    >
    > So, one of these things is not like the other, one of these things,
    > doesn't belong, can you tell me which one of these is not like the
    > other, before I finish this song?* (Hat tip to Sesame Street).
    >
    > So... You MUST access services authenticated by OSP via the configured
    > URL. Period.
    >
    > So, have you tried the proper URL?* Does that work?
    >
    >

    Greetings,
    If you have switched from http to https you have to update the
    redirect and server information in both configutil and configupdate. ID
    Gov has to know and so does OSP.

    --
    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    Micro Focus

    I not switch http to https..., just only installed with certificate https 8443

    I cant open configutil in idrpt, is in \idrpt\bin\configutil.cmd -password 'dbpassword'

  7. #7
    Join Date
    Dec 2018
    Posts
    21

    Re: OSP error

    Detail error when enter IG reporting,


    http://prntscr.com/n3qxb9

  8. #8
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: OSP error


    >>>>> Is it exactly:
    >>>>> http://w16qavidgsrv01.ad.gi.cl:8080/ at its base?
    >>>>
    >>>>
    >>>> Is not the same...
    >>>>
    >>>> Detail ism.configuration.properties:
    >>>>> com.netiq.idm.osp.url.host = https://w16qavidgsrv01.ad.gi.cl:8443


    Ok, so your install is configured to use HTTPS on port 8443.


    > I not switch http to https..., just only installed with certificate
    > https 8443


    Ok. So you installed to 8443, over SSL.

    Why then were you trying to connect over HTTP (no SSL/TLS) on 8080 then,
    which was your original question.

    > I cant open configutil in idrpt, is in \idrpt\bin\configutil.cmd
    > -password 'dbpassword'


    Edit the configutil.cmd file. Look at the _db_user and _db_url and make
    sure they point at proper values.

  9. #9
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: OSP error

    On 3/27/2019 1:26 PM, sosix wrote:
    >
    > Detail error when enter IG reporting,
    >
    >
    > http://prntscr.com/n3qxb9


    Screen shot is ALMOST helpful, but you would need to show us the URL bar
    to see specifically what URL you are trying to reach.

    I.e. Are you connecting on http and 8080 or https and 8443?



  10. #10
    Join Date
    Dec 2018
    Posts
    21

    Re: OSP error

    Quote Originally Posted by geoffc View Post
    On 3/27/2019 1:26 PM, sosix wrote:
    >
    > Detail error when enter IG reporting,
    >
    >
    > http://prntscr.com/n3qxb9


    Screen shot is ALMOST helpful, but you would need to show us the URL bar
    to see specifically what URL you are trying to reach.

    I.e. Are you connecting on http and 8080 or https and 8443?
    first, login in IG with https://w16qavidgsrv01.ad.gi.cl:8443/#/landing

    then, enter in identity reporting module (button in IG -right upper corner-) and re-direct to https://w16qavidrsrv01.ad.gi.cl:8443/IDMRPT/

    and after accepting the certificate, shows the following error: http://prntscr.com/n3qxb9

    rgs,

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •