basic setup

[deactivated user]

Hello All,  We are working through hoops of getting budgets for training this year which is not easy, so I am trying to learn this on my own. Please pardon me for asking such basic stuff and may even be redundant. Appreciate if you can direct me to any pointers in the process.

 

I have installed and setup a v8.4 gateway with SQL and created a policy manager to administer the gateway. I connect to the Gateway through policy manager using:

 

http://gatewayhost:8443/

 

I have a RESTful web service which is currently protected by SiteMinder , but I would like to route those API calls through api gateway, where API gateway challenges the user with basic authentication, validates the user through our AD connection(this connection has been created and vertified through policy manager) and upon successful authentication, routes the user to backend service.

 

For this, I have used: 'publish RESTFUL service proxy with WADL' , chose manual entry as there is no WADL.

 

second screen:

Service Name :  Test

Resource Base URL:   https://application server host/app/resource/tree

Gateway URI: http://gatewayhost:port/app/resource/tree

 

Note: Gateway URI is prepopulated with the http://gatewayhost:port/ , I am assuming port means 8443. and the URI is populated based on Resource base URL.Next screen I setup authentication only t certain users and created the service. The Policy is Active.

 

Testing:

 

I goto http://gatewayhost:8443/app/resource/tree

Instead of getting the basic prompt, different browsers behave differently.  IE downloads a file with some junk, in mozilla the same file content, gibberish message is rendered in the browser.

 

What is the best way for troubleshooting:

 

My ssglog.properties file has the following:

 

#

# SecureSpan Gateway logging level configuration

#

 

Do I have to use the log sinks?

[ADNAN Siddiqui]

Use SOAPUI to test, debug your policy and add context variables to see whats going on, press F1 for more help.

[deactivated user]

Thanks Sir, for that tip. I get an error saying:

 

Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation." xmlns:l7="http://www.layer7tech.com/ws/policy/fault

 

So it looks like my req is reaching my api gateway but I may have misconfigured my service so it does nt know where to forward.

 

Is it possible for you to print a basic service here in this thread, that I can use as a reference? Appreciate your time.

[Stephen Hughes]

Anil,

 

The error you have included "Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation." xmlns:l7="http://www.layer7tech.com/ws/policy/fault" occurs for the following reasons:

 

1) The URI that you are attempting to send the request to does not exist as the service URI is an exact match including case. Wildcards can be included to allow for additional variations.

2) The Service endpoint is a SOAP service and the SOAPAction and operation in the request does not exist in the WSDL. You can bypass this by opening the service properties in the Policy Manager and select the WSDL tab. From the WSDL tab, check the "Allow requests intended for operations not supported by this WSDL" and click OK.

 

Additional information can be found by searching the online documentation under the title: Understanding the Service Resolution Process

 

Sincerely,

 

Stephen Hughes

Director, CA Support

[didsi01]

Just a quick question, you are using http with 8443, either try http with port 8080 or https with 8443