This API Fortress Helper utility allows you to access files via an API.
This API Fortress Helper utility allows you to access databases via an API.
Place the package in a machine that has access to the databases that you wish to use, and which could be reached by API Fortress via HTTP.
As a default, the system will connect to PostgreSQL, but you can configure it to run against any DB that can be accessed with JDBC.
Of course, this requires a bit more configuration located in apps/db-api-helper/db-api-helper.xml. Next steps are pretty straight forward.
Look for the following element:
<db:generic-config name=”Generic_Database_Configuration” url=”jdbc:postgresql://172.28.0.1:5432/apipulse?password=jk5112&user=apipulse” driverClassName=”org.postgresql.Driver” doc:name=”Generic Database Configuration”>
If you plan to use another database, you will need to download the matching JDBC driver, place it in the apps/db-api-helper/lib directory, and configure the flow accordingly.
In our example, hitting the route like this…
curl -H ‘content-type:text/plain’ -d ‘* from auser’ http://<machine_hostname>:8092/db/select
…will trigger a select query that will return the result as a JSON array payload.
INSERT, UPDATE, DELETE routes are also available and they work similarly.
It’s as easy as “sudo docker-compose up -d”.
If you are using an on-premises deployment and would like to set up single sign-on (SAML 2,.0) follow the below instructions.
Step 1: Activate it
Whether you’re using a docker-compose or a Kubernetes deployment, introduce the following environment variable:
Step 2: Configure it
The provided “saml/saml.properties” file contains all the configuration keys necessary to the SAML functionality.
onelogin.saml2.sp.entityid: identifies the SP
onelogin.saml2.sp.assertion_consumer_service.url: where the response from idp is returned after an authentication request
Onelogin.saml2.sp.single_logout_service.url: where the response from idp is returned after logout request
onelogin.saml2.idp.single_sign_on_service.url: where the SP will send the Authentication Request
onelogin.saml2.idp.single_logout_service.url: where the SP will send the logout request
onelogin.saml2.idp.x509cert: public x509 certificate of the IdP
onelogin.saml2.sp.entityid = apifortress
onelogin.saml2.sp.assertion_consumer_service.url = http://apif.example.com:8080/app/web/login/acs
onelogin.saml2.sp.single_logout_service.url = http://apif.example.com:8080/app/web/login/sls
onelogin.saml2.idp.entityid = https://app.onelogin.com/saml/metadata/7037e41d-4ab4-417a-b0a2-c4e2f580faf2
Onelogin.saml2.idp.single_sign_on_service.url = https://apifortress.onelogin.com/trust/saml2/http-post/sso/917654
onelogin.saml2.idp.single_logout_service.url = https://apifortress.onelogin.com/trust/saml2/http-redirect/slo/917654
onelogin.saml2.idp.x509cert = —–BEGIN CERTIFICATE—–CERTIFICATE HASH—–END CERTIFICATE—–
Further changes can be applied to the expected properties:
#in IDP one of MANAGER,DEVELOPER,ANALYST
By altering these configuration keys, you change the name of the property that’s being sent by the IDP. As a default, the required properties are:
LEVEL represents the level of the user within API Fortress and can be one of the following values: MANAGER,DEVELOPER,ANALYST
If the field is not provided, MANAGER is assumed.
The admin status can only be set via the API Fortress configuration panel.
Note: there may be other configuration keys to be altered based on the IDP requirements.
Step 3: Mount it
Mount the provided “saml” directory to the location: /usr/local/tomcat/webapps/app/WEB-INF/saml
If Kubernetes is being used, ConfigMaps will achieve the same result.
Step 4: Restart API Fortress
Restart the API Fortress dashboard(s).
**To learn how to import a connector click here**
This connector allows you to connect your API Fortress instance with your StatusPage instance. When a test fails the connector will open an incident in StatusPage, the next time that same test runs and passes the connector will resolve the incident in StatusPage.
What you will need from your Status page account is the Page ID and the API key, both can be found by logging into your StatusPage account and going to the manage account page. Then click on the tab names “API”:
Next we will configure the connector in API Fortress:
Don’t forget to add the alert group the project you want the connector to work for:
You can generate a test draft from an API managed in Axway.
- On the test interstitial page there is a “Build from Axway” button, click it
- Enter the Username, Password and Base URI for your Axway account (this is your base URI, not including the path eg. https://api.axway.training:PORT, please note that the http/s is required)
- Then choose the API Project that contains the API you would like to generate a test from
- Then for the API you want to generate a test from, click on the lightning bolt on the right side
- You now have a high level test created from the API in your Axway account. Run the test as is, or modify it to add more logic!
Click here if you would like to learn what to do from here.
We now have an integration built out with Curiosity Software’s Test Modeller. This integration allows you to power your API Fortress tests with modeled data that was generated in TDM.
Below are the steps to integrate TDM with APIF:
- Create an API Fortress test that will be used with TDM data.
- Generate Webhook for project that will use TDM data:
- Test Modeller:
1. Go to Profile -> Connectors
2. Click “Add Connection”
3. Set up the API Fortress connector in Test Modeller
1. Connector Type: choose API Fortress
2. Profile Name: Give the profile a name (recommendation: this should match the API Fortress project name for organizational purposes)
3. Url: This is your API Fortress domain up to the “/app” part (example: https://mastiff.apifortress.com/app/)
4. Username: This is your API Fortress login username
5. Password: This is your API Fortress login password
6. Project Hook: This is the API Fortress hook that we created earlier in API Fortress. (use the string at the end of the url, for example https://mastiff.apifortress.com/app/api/rest/v3/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxx
4. Save the connector
Now you have your integration between TDM and API Fortress complete, create some models and run tests with multiple input sets easily!
To watch a video on this process including how to create model and push data to APIF and run the test click here.
Here is a quick guide to setting up and using the PagerDuty connector.
Note: this connector does not come pre-loaded out of the box, and will need to be loaded separately. To learn how to load the connector into your API Fortress instance click here.
- Go to settings page
- Click on “Alert Groups”
- Create a new group or add a connector to an existing alert group
- Add a new connector
- Choose the PagerDuty connector
- Configure the connector
- routing_key is the integration key generate for a service in PagerDuty. The routing_key can be generated here
- severity is the level the alert should be sent as. (critical, error, warning, and info)
- dedup_key is a key that will allow to you match a triggered alert with a response for that alert
- event_action is the action you would like the alert to take. (trigger, acknowledge, and resolve)
- Go into project settings for a project you would like PagerDuty alerts set up for
- Add the alert group that contains your PagerDuty connector to this project
Here is a quick guide to load up a new connector into your API Fortress on-premises deployment.
You can find all the connectors here: https://github.com/apifortress/connectors
API Fortress can absolutely integrate with your JIRA setup. However, because not all JIRA boards are created equal, if you would like a connector set up for your specific JIRA board please out to firstname.lastname@example.org
We will then gather the appropriate information and build you a custom connector for your JIRA setup.
**To learn how to import a connector click here**
Here is a quick guide to setting up a Hipchat integration.
First generate your Hipchat personal access token. To do so go to https://[your_company].hipchat.com/account/api
Then get the room id you would like to send the alerts to, it can be retrieved in the room details page “API ID”
If you are migrating to Slack, we also have a connector for that! Click here to see how to set up that integration.