This is not an Atelier issue, but an issue of general concern. A system administrator might specify authentication but also allows for unauthenticated access. The instance will try to authenticate and if this fails will determine if there is another authentication option.

The authentication mechanism of unauthenticated was helpful at the time when it was created, but not anymore. It is too easy to leave a server wide open; something nobody can afford anymore. The minimal installation option will go away, and with it the default of having unauthenticated being enabled. Atelier is already based on the concept that all access to a server requires authentication.

Stay tuned for more changes in the area of product installation and install modes.

Hi Maarten,

is this still an active question or are you all set?

Respectfully,

Andreas

The installation does in general not offer the option to place the core files of the system in different locations. Some aspects like new databases and journal file location can be changed later, as part of the system configuration. You seem to have already found the correct documentation for this.

The title of the post is not quite correct. You would like to resolve something in the authentication step, not the authorization step. Please take a look at the ZAUTHENTICATE.mac in the SAMPLES namepace that includes a large array of options and code examples (most can be used just by uncommenting them). It also includes an example of performing 2 factor authentication. For this to work you have to validate the user's credientials first and then step into the 2 factor part of the authentication. Let me know if this helps. If not I will get you a more concrete implementaiton of ZAUTHENTICATE.

(Also please make sure that your authentication options for the service has the right list of options (in your case problably only delegate authentication))