FAQ BlueX

Operators typically require about 1 hour of training to learn how to perform their operations in BlueX.
Administrators typically require about 1 day of training to learn how to perform day-to-day administration and troubleshooting on a BlueX environment.
System integration engineers typically require about 1 week of training to learn how to create new custom workflows and configure all the details for a full-custom BlueX environment.

BlueX supports all current versions of Active Directory. Multiple directories can be supported from a single BlueX installation.

No changes or schema-extensions in the AD are required for BlueX to support your AD. If custom schema elements exist in your AD these can be supported by BlueX. BlueX does only require an account with sufficient permissions to access the AD.

No, BlueX does not require an Active Directory. BlueX offers a very powerful Active Directory integration for use when required, but no dependencies on the Active Directory exist in BlueX.

In most cases BlueX requires a database, although some deployments without a database do exist. BlueX does not install a database of its own, but requires a dedicated database (not a dedicated database server) for most functionality. If a supported database server is available, the BlueX database may be created on the existing database server, otherwise a database (server) may be installed with the BlueX server.

BlueX cannot send SMS messages, but BlueX could send e-mail to a mail-to-SMS gateway.

BlueX can send e-mails if an SMTP server is available. BlueX does not provide an SMTP server of its own.

BlueX can provide all kind of printed content. BlueX is often used to print PIN-letters or ‘Secure PIN-mailers’, cover letters, envelopes, package-labels and such. Any printer supported in Windows can be used to print the desired documents.

Just printing the surface of the smartcard is supported by BlueX using any smartcard printer supported in Windows.

Using a smartcard printer for batch-personalization of smartcards that includes both digital personalization (writing to the chip) and surface personalization is also supported by BlueX, if the following requirements are met:
A smartcard printer that is supported by BlueX is used, and this smartcard printer has a build-in PS/SC compliant smartcard reader that is supported by the middleware.

BlueX uses the middleware to access smartcards and USB-tokens. If the smartcard/USB-token is supported by the middleware and the middleware is supported by BlueX, BlueX can support the smartcard/USB-token.

BlueX supports different middleware products from different vendors, but does not include smartcard middleware of its own. For optimal performance and widest range of functionality we recommend using BlueX in combination with the SafeSign IC Middleware. More information on supported middleware products is available on request.

No, BlueX does not support the MS stand-alone CA. The MS stand-alone CA is suitable for some specific use-cases that are not within the scope of a common BlueX deployment.

BlueX supports the Microsoft Windows 2008+ Enterprise CA.

BlueX supports a range of certificate authority products of different vendors, and does not include a certificate authority of its own.

For a BlueX server machine, hardware at least equal to the recommended hardware specification for the operating system is a good start. Additional hardware requirements depend completely on the deployment scenario and the number of transactions demanded from the server. These requirements can only be discussed on a deployment specific basis.

For a BlueX Remote Component client, hardware at least equal to the recommended hardware specification for the operating system will do fine. Installation footprint will be limited to several MB of disk space.

For a simple BlueX Operator client, any hardware sufficient to run a supported browser will do.

Operator authentication requires a personal digital certificate. This may be a certificate installed in the browser or a certificate on a token/smartcard. In cases where a token/smartcard is used, smartcard middleware is required on the client.

Microsoft Internet Explorer version 9+. And the latest versions of Mozilla Firefox, Apple Safari and Google Chrome.

For a BlueX server machine, Windows 2008+ server operating systems are supported.

For a BlueX Remote Component client, Windows 7+ and Windows 2008+ server operating systems are supported. More information is available on request.

For a simple BlueX Operator client any operating system could be used, provided a supported browser is available.