Introduction

Through the years we have provided in our standard documentation many known product limits. Others are not documented because they simply exceed the design so generally we don't even think about them. (For example, we don't document the fact that our Active Directory Sync service doesn't run on a Mac.)

Further, with each release of the product, the restrictions, the things it cannot do, get generally smaller and we try to be more and more flexible.

In addition, we are well aware that many customers consider the product to work well in their environment even though we document that it doesn't work and/or isn't supported.

Often this is because they have found a way around some of the specific limitation(s) and/or they have developed a 'hack' that works with that current version of the software.

The loginHub in general is documented for the environments it does handle, not the environments it doesn't. There are literally mlllions of ways to setup networks, the LoginHub relies on very specific conditions, and while the number of environments and flexibility of the LoginHub increases with each release, it cannot, by its very nature work outside of several of the millions of options.

This is, by its very nature, the biggest design limitation of the LoginHub.

My Hack or work-a-round worked the last release: you have a bug my hack doesn't work anymore.

Sorry, that's not a bug. We do not support that, and any assistance will be billed at normal rates.

Does 'not supported'/'Not support' mean you won't help me with problems?

No, what it means is if a problem is related to a setup that isn't in the set that we support or exceeding limits or doing things that are not supported we simply bill those things by the hour and we will not likely try to fix them as quickly as we do bugs, if ever. But things that are not related are still supported by our normal terms. It also may mean that when we offer a solution, it may be an extra cost product.

Can I tell you about a 'bug' I find when I ignore the limitations?

First of all – this is commonly how people say it to us, but don't be surprised if we say 'That is not a bug, that is a design limitation' or 'that's not a supported configuration'. We, and most people, define a bug as 'Something that it is designed to do and doesn't'. But we understand many people define a bug as 'something I don't personally like'. So we might say 'that's not a bug'…

But then we DO listen, and we consider when and how we can have our software not have that 'issue.' If you want it changed sooner than we decide (or if we decide we aren't interested in 'fixing' it) then you can talk to us about having a customer sponsored feature – a feature you pay in part or in whole for.

Once we understand your configuration, we do try to add it to our supported configurations.

Some limitations that may or may not be obvious to you

We picked these because customers have told us in the past that they are ignoring the documented limitation and/or are surprised by the limitation.

You must use IE

To setup the DataHub, we use Silverlight, and Silverlight only runs in IE.

DataHub does not run in a transaction

A transaction means that if something crashes, the database will roll back to the state it was before. The problem with bulk loaders like DataHub is that this can mean it takes hours to run (causing timeouts) and can consume Gigabytes of memory and Hard drive space as SQL server preserves enough information to 'roll back' to the previous state.

So if there is a network crash, computer crash etc.., during the import, it may be necessary to do manual fixes and/or restore from a backup. While this is true, in real life, it almost never happens.

UI only works for small volume 'test' data sets

The ui is designed for low volume use/imports. It may time-out with large imports (the service doesn't have this limit.)

Other limitations – practical or 'breaking' you have run into and think should be in this document?

Let your support person know, preferably by email, and we'll look at adding it to the next version of this document.