| Subcribe via RSS

Quick Guide to Rebranding SailPoint IIQ

January 18th, 2012 | No Comments | Posted in IdM Engagement, Vendor Specific

So you’ve got Sailpoint IIQ all installed and humming on your enterprise servers, and your boss walks in and says “My boss says the CIO wants this rebranded for better internal look and feel, to keep confusion down for identity self-service requests. Can you have it done by Monday?!”

Your answer, even if it’s Friday, should be “Yes, sir!!” Here’s how you can do it, covering just the basics. In this exercise, we’ll cover rebranding:

  • The login banner page
  • The IIQ headers on each page, and…
  • The overall CSS colors on each page providing the final L&F

Let’s get started.


The tools and “skillz” you will need (as they say) will actually lean more on the graphics side than on the Java or HTML development side for this exercise. In fact, other than careful and proper placement of the resulting graphics files inside your deployed application and application server file system, graphical capabilities and understanding of CSS are going to be your primary concerns. If you are not very good at handling a graphical editor like Adobe Photoshop or GIMP, now’s the time to call your friend, Sally, over in Marketing to lend you a hand.

Assuming you know where Sailpoint IIQ is “rooted” on your application server, we’re going to graphically reconstitute a few files. We’ll assume a Tomcat installation here, which should carry over quite nicely for a JBoss AS installation as well. WebSphere, Glassfish, WebLogic and you other app server flavored peeps out there, try to follow along.

For Tomcat, assuming an installed/deployed path of /srv/tomcat6/webapps, you should/would have /srv/tomcat6/webapps/identityiq for your application root. So then, we’re going to graphically reconstitute:

  • $APP_ROOT/images/login.gif
  • All the header*.gif files in $APP_ROOT/images and…
  • identityIIQ-logo.gif

Furthermore, we’re going to, at a bare minimum, twiddle the background-color CSS attribute on five (5) CSS files. We’ll detail all that when we get to the section on CSS.
More »

Tags: , , , , , , , , ,

Google Chrome Natively Supports GreaseMonkey

Have you ever gone to a site and wished you could “tweek” the site to suit your needs a bit better? Or wished it looked or was laid out just slightly differently? Wish you could change the look and feel or create your own theme for it? The content and overall functionality is what you want, but you just want to make a tweek, especially one that suited you personally and you knew would never be requestable or a truly feasible feature to add for everyone?

Well, a while back, when Firefox held the number two spot for all browsers (which it recently has lost by the way, and I think for good reason, though I’ll not get into the whys here), you could accomplish exactly the above if you installed a Firefox extension called GreaseMonkey and held a commanding understanding of Javascript. (And you can still leverage GreaseMonkey if you happen to still use Firefox.)

I don’t have the time here to get into all of what GreaseMonkey can do for you. (Though the capabilities are QUITE extensive; Check that out on your own here.) I just recently had a need to update a site and customize it slightly to suit my needs, and, being pretty much an ardent Google Chrome user now, I decided to look into the possibility of using GreaseMonkey on Google Chrome. GreaseMonkey was fantastic on Firefox and, while I’d not run into a need for it under Google Chrome up until now, I did definitely desire to leverage it suddenly.

Wow, was I ever surprised! Google Chrome actually supports GreaseMonkey scripts NATIVELY. Your GreaseMonkey user script (as they are called) is simply viewed as a Chrome Extension. So all you have to do is write your script, drag and drop it into a Google Chrome window, and viola! You have a custom Chrome Extension or natively supported GreaseMonkey script, however you want to look at it.

It turns out that my personal use case is suitable as a quick demo of just how powerful this feature can be. It turns out I have this nasty habit of entering my timesheet for the week in the wrong week. I do this about 50% of the time, and it’s a real time killer when I do it, because the only way I can correct it is to back out each time entry individually and that takes a number of key clicks and screen changes. What I really need is a quick popup reminder to remind me to enter my time for the correct week when I first get into the initial time entry screen. My use case is as simple as that.

// ==UserScript==
// @name           NetSuite Timesheet Reminder
// @namespace      http://www.TechnologEase.com/GreaseMonkey
// @description    Reminder to fill in timesheets correctly!
// @include        https://system.netsuite.com/app/accounting/transactions/timebill*
// ==/UserScript==

// Just send an alert - that's it!
alert( "Make sure you enter your time for the CORRECT WEEK, Bozo-brain!!" );

Works great. Now next week and every week thereafter, I’ll get a reminder when I first enter the initial time entry screen and that should be enough to save me future headaches. :-)

GreaseMonkey just uses plain ol’ Javascript so, coupled together with something like JQuery and CSS 2 or CSS 3, you can imagine the power this brings to you for any and ALL web sites, if you can harness the power of Javascript for yourself. And Google Chrome supports this natively.


Related Content

Tags: , , , , , ,