GeoNames Web Services API

Provides convenient services like who would want search nearby Hotels when they visit a new city or who is in a medical emergency need nearby Hospitals.

Following URL get more about GEONAMES web services.

Gisgraphy is an open source framework for geolocalisation and geocoding. This framework uses
GEONAMES web service API to find the locations.

Find more click here.

The following are GeoNames WebServices

1. findNearbyPlaceName
2. findNearbyPostalCodes
3. countryCode
4. countryInfo and many more

findNearbyPlaceName: 

      

     Here nearby place can be populated by giving longitude and latitude.

     

     The return values we can select a format from available formats like XML, JSON.

           
     Find more click here on the following link for findNearbyPlaceName in Gisgraphy.

findNearbyPostalCodes:

    It can find nearest places against to either given longitude, latitude or postal code.

    The return values we can select a format from available formats like XML, JSON.

    Find more click on the following link for findNearbyPostalCodes in Gisgraphy.
   
    https://services.gisgraphy.com/static/leaflet/index.html#

countryCode:

    In this service, we will get Capital, Population, Area in square km etc., against by giving
    a Country name.

countryInfo:

    This service will return the iso country code for the given latitude/longitude.

OAAM policy risk evaluation in OAM policies(OAM 11g Identity Context)

OAAM policy risk evaluation in OAM policies

Demo Video: https://youtu.be/NOAW2JE0km8

Steps: 

Login to OAAM Admin Console

Search for DAP token version property and change to v2.1 

Update OAAM TAP Token version from v2.0 to v2.1 in oam-config.xml file. 

Note: Since I have integrated OAM + OAAM already I changed OAM DAP token version in oam-config.xml file from "v2.0" to "v2.1". Else you can provide version v2.1 directly while executing ThirdParty TAP registration command(while OAM + OAAM integration)

Create a group for to hold all the restricted IP Addresses as shown in the screen shot below.

Add IP Address to the group

Create new OAAM Policy as post authentication

Create rule and condition to determine if user login in from restricted IP Address or not.

Select IP Address Group created initially from the drop down 

Click on Results Tab and enter score as "1"

Click on "Group Linking" and select "All Users"

Login to OAM Admin Console and click on "Application Domain".

Select the "ohs_webgate". This is the OHS webgate I have already created and used OAAM TAP Authentication Schema to protect resource.

Click on "Authentication Policies"

Click on "Protected Resource Policy"

Click on "Responses"

Add response as shown in the screen shot below.

This "session_risk_level" is the session attribute that passes as part of DAP token from OAAM to OAM after policy evaluation created in the above steps. 

Click on "Authorization Policies"

Click on "Protected Resource Policy"

Click on "Conditions"

Click on "+" sign

Enter the condition details as shown in the screen shot below.

Add Condition Details as shown in the screen shot below.

This is the "session_risk_level" session attribute returned from OAAM and the attribute value that gets "1"

Click on "Rules" tab and add new rule in the "Deny Rule" list and click "Apply".

Now test the protected application from two different machines!!!

-- Siva Pokuri.

Remove/Disable Authentication Pad's from OAAM 11g Login Pages

There are ways to remove/disable OAAM Authentication pads from login pages, one way is by modifying OAAM AuthenticationPad Policy trigger combinations as shown in the below screen shot.

-- Login to OAAM Admin console

-- Navigate to policies and click on "OAAM AuthenticationPad Policy" and click on "Trigger Combinations" tab.

-- Modify the trigger combinations as shown in the below screen shot and click "Apply".

-- Then try login and test the functionality

Hope this helps some one out there!!

-- Siva Pokuri.