Monday, January 28, 2013

QT001: Preventing Your Salesforce Integration Password from Expiring

Quick Tip 001: Preventing Your Salesforce Integration Password from Expiring

First A Note on Password Policies . . .

Before we get started I think its important to note that good password policies are essential for protecting your data, and changing your password occasionally is very important and should not be overlooked.  That being said, having your password expire for your integration user can be a disaster for your business.

Don't Let an Expired Password Stall Your Integration

Its midnight on Saturday night and suddenly your phone is inundated with emails about errors in your Integration between your ERP and  You haven't made and code changes in months and have no idea why.  After digging through your logs you realize, the password for your integration user has expired.  You now need to login and change your password, but first you have dig up that secure password you created when you setup the account.  You may be tempted to disable password expiration for your organization to avoid this problem again, but then there won't be anything to ensure that your users are rotating their passwords.  Well there is a solution.

Using Permission Sets to Prevent Passwords from Expiring

You want to use password expiration enforcement for your users but you don't want to be caught off guard by having your Integration User get locked out of the system because of a password expiration. has a solution for this problem, you can create exceptions to your security policies for specific users with Permission Sets.  

Create a Permission Set

Create a new Permission Set by navigating to the setup page.  Then go to Manage Users > Permission Sets and click "New" give the Permission Set a Label and unique API Name and click Save.

Add Password Never Expires Permission

Go to System Permissions and click Edit, then scroll down to "Password Never Expires" (or search for it) and check the box.  Click Save.

Assign the Password Never Expires Permission to your Integration User

Go to Manage Users > User, find your integration user and click on the username.  Scroll down to Permission Set Assignments and click "Edit Assignments" then find the Permission Set you just created and assign it to the integration user via the add arrow button, then click save.  

That's it, you are done, you will never be caught off guard by a Password Expiration again . . .

Remember however, that good password policies are a must to protect your data.  Your integration user should be a secure password, it should be kept secret and it should be changed from time to time. will still enforce your policies with respect to secure passwords, and it will still require normal users to change passwords, but it is now the responsibility of the administrator to change your integration user's password occasionally.

Thursday, January 24, 2013

IBM Cast Iron Version

Cast Iron Version

IBM has released a new version of CIOS version was released on 12/14/2012.  You can view the details on the Release Notes and Online Help by following the links.

Bug Fixes and Testing Impact

From the Bug Fixes in the Release Notes, the one that jumps out as a potential target for regression tests is this one: 


Based on the details noted, it appears that some users using the database connector may experience a change in the way times are stored in the database.  This is likely database specific and would only impact users if their appliance timezone is not set to GMT.

New Feature Highlights

Here's the short list of new features, we'll dig deeper into some of the new features in later posts:
  • REST and JSON Support: Long awaited support for JSON and expanded suport for RESTful web services in the HTTP connector.  See this post for more details.
  • New Connectors: Workday connector, RightNow SOAP API connector, Zuora connector have been added.
  • New Connector Activities: HTTP, JDE, SAP, and PeopleSoft connectors have new activities.
Update: IBM has Issued an Alert for this release due to a critical issue in which the WIP partition could fill up and prevent the appliance from operating normally.  See the Alert from IBM for further instructions should this happen to your appliance.

Ominous VisualForce "An internal server error has occurred" Error

If you have ever been developing a VisualForce page for and received an internal server error, there may be a quick work around.  I hit this problem a few days ago and spent hours trying to figure out what was going wrong in my code.  There were no errors in the Developer Console and it appeared that my code was completing successfully.  Well, as it turns out, it wasn't failing inside my code, there was something else going wrong on the server side.

I still don't know exactly what I was doing to cause the error, but it seems that the error was related to the Development Mode editor for VisualForce.  I disabled the "Show View State in Development Mode" setting (if you're looking for it, its on the user settings page in setup go to Setup > My Personal Information > Personal Information).  After disabling the view state setting, the error went away and my page is rendering correctly.

Welcome the Conexus, Inc. Blog

Welcome to our blog.  Your source for the latest information about Conexus.  Here you can find out what is going on in the Conexus universe, as well as tips and tricks from our experts in IBM Cast Iron, Boomi, Informatica, and more.