What are the steps to create a webapplication for a web site that is in our data center ?
Common information on creating a webapplication. Example application is called FootPrints and this application lives in customers data center.
x.x.x.x = the ip address of the stoneware relay.
First thing is to know if this app will be hidden behind portal eventually and not available directly from public internet.
Let's assume that the firewall will eventually be changed and you won't be able to get to this server directly from the public internet without logging into the portal.
1) Open webadmin, right click on Applications Admin and chose Publish Virtual Application
a. Name: footprints
b. Use default context
c. Host name : footprints.school.com (this is the real address to get to the real server)
d. Port : 80 / Internal server uses SSL : off
e. Virtual dns name : wnfprints.school.com (this is a unique dns name not already in use at your site / portal)
f. Startup url : /MRcgi/MRlogin.pl ( I got this by going to the site and seeing what the login page url was)
g. Menu for Link : added to Personal Services/Applications menu / Default for new window
h. Added to portaladmingroup (you can assign to who ever should get this)
2) Now that the webapp is created, I have to modify my workstations host file with x.x.x.x wnfprints.school.com (you would change your dns servers with this information once tested)
3) Log off and back in so I have rights to the new application link
4) Test the application to make sure it works PRIOR to trying to do SSO.
5) When I load the page, I notice that it steals the entire window.
a. Go into webadmin and set the footprints-link to New / Native window to help prevent this.
b. Log off , back in and try again
6) To verify that webapp stays inside its virtual dns name of wnfprints.school.com I right click on the footprints link and choose open in new tab/window
a. Login and test app, make sure that url stays at wnfprints.school.com
7) Now on to SSO
a. Go into webadmin and find footprints webapp
b. Right click on footprints webapp and choose SSO Client form Wizard
c. Right click on #1 to add that to your favorites (need to use IE or FF to do this)
d. Click on #1 to launch app
e. Click on favorites and find the new favorite you just made in b)
f. Screen should split
g. Click Start SSO Building Process
h. Choose Form 3 (login action /mrcgi/mrlogin.pl)
i. Choose Next
j. Put check box next to USER, PASSWORD
k. Click Next
l. I will enter the script that triggers the login manually
i. Do the way the page is designed, it does not see the LOGIN button
m. Click next
n. Info screen comes up, choose Create this SSO Form
o. Click Close wizard.
p. Close the footprints window
8) Click on footprints-app in webadmin
9) Click on Authentication tab
10) Click on Footprints-app-form and then the magnifying glass
11) Go down to Form inputs and fill in your username/password for the values user= and password= (we hard code for testing purposes)
12) Click Save
13) Go to footprints webapp and click RELOAD
14) Click on Footprints link and test if it SSO's
15) Click the Logout link on footprints, verify that it does not re SSO upon logout.
a. This works as expected
16) Now let's change it to use dynamic credentials so it is not hard coded for one user.
a. I will assume that since this is a MS ad webNetwork install that attr:samaccountname will work.
b. Go back to the cn=footprints-app-form,ou=external_relay_001,ou=stoneware,dc=school,dc=com
c. Change the hard coded username/pass to attr:samaccountname and password by choosing from the list of attributes.
d. Save changes
e. Go back to the footprints-app object and click reload so the changes take effect.
f. Launch footprints link and test that change works.
17) Assign footprint-app webapp to the proper RELAY objects and wait for them to auto load
18) Assign the footprints link to the proper people
19) Modify the DNS tables inside and out for wnfprints.school.com and make sure they point to the proper relay.
a. For example, on the dns server for the public internet, that should point to x.x.x.x or wnfprints.school.com can be a cname of portal.school.com
b. Verify dns changes took using nslookup
c. Login from outside your network and test
d. Login from another machine (other than what you used to create webapp) and test on inside of your network.
So this application was pretty straight forward, the login page is a little different because it has 2 forms. One for the username and one for the password which is a bit odd, but the wizard was able to handle it.