Security

last person joined: 19 hours ago 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

When setting up a Google admin context server We get a non-public domain error back from Google.

This thread has been viewed 8 times
  • 1.  When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 19, 2016 02:49 PM

    When setting up a Google admin context server We get a non-public domain error back from Google. The error is:

     

    Error: invalid_request

    Invalid parameter value for redirect_uri: Non-public domains not allowed: https://OPCS-ClearPass/async_netd/mdm/oauth/google

     

    When we setup Google it had we had the correct public domain information: https://OPCS-ClearPass.opschools.org/async_netd/mdm/oauth/google



  • 2.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 19, 2016 02:56 PM
    Did you defined FQDN for ClearPass under Administration > Server Configuration > System Tab


  • 3.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 19, 2016 03:08 PM

    Yes I did..

     

     OP-FQDN.JPG



  • 4.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 20, 2017 12:07 PM

    Hello,

    Is this problem solved. I am running in exactly the same problem

    clearpsss 6.6.8. and configured clearpass with a FQDN. So same problem as above,  It seems that Clearpsss goes out without the FQDN.

    In the URL that pops up with the error, there is no FQDN  but just de clearpass hostname. Manual  adding/modifying this URL with the FQDN name gives a correct  responce from google. So how can we solve this!

     

    Gerrit



  • 5.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    EMPLOYEE
    Posted Oct 20, 2017 12:27 PM
    Enter the ClearPass FQDN in the FQDN field in the server configuration.


  • 6.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 21, 2017 03:29 AM

    That's is  what I configured,( before posting) but didn't help

    I configured the FQDN name in Server configuration field.  

    Clearpass still ony uses the Hostname!

     

    Gerrit

     



  • 7.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    EMPLOYEE
    Posted Oct 21, 2017 05:41 PM
    Screenshot of your server config screen please.


  • 8.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    Posted Oct 22, 2017 05:42 AM

    Hi,
    Here is the screenshot of my server config, as you can see the FQDN is configured
    FQDN.jpg
    When I Authorize Clearpass in the context server
    Clearpass-auth.png
    I receive the message:
    Invalid parameter value for redirect_uri: Non-public domains not allowed: https://cp-hak3/async_netd/mdm/oauth/google
    When I manually modify the URL in the popup screen of the error to https://cp-hak3.hak3.nl/async_netd/mdm/oauth/google
    Google seems te accept this.

    Gerrit






  • 9.  RE: When setting up a Google admin context server We get a non-public domain error back from Google.

    EMPLOYEE
    Posted Oct 22, 2017 08:05 AM
    Please open a TAC case.