Additional Domino Server Support
JoelProminic opened this issue · comments
In the near future we will want to add support for additional Domino servers. Currently we only support standalone servers.
This will require a different set of parameters than the standalone installation. Here is an example of the parameter needed from MyAccount:
@MarkProminic may need different parameters as we figure out the details for the provisioner.
@piotrzarzycki21, we would like to move forward on this interface. Most of Prominic's customers will have existing servers already, so this use case has been becoming more important. @MarkProminic is working on the backend for this, and we'll let you know when it is ready to test.
@JustinProminic made a mockup, but it is already a bit obsolete after more discussion. I decided to represent this as a table instead. but I can create a mockup if this is confusing. This should look similar to the current Standalone interface, but it has different parameters. The Notes are for our discussion, and should not be included in the actual interface:
| Configuration (#XXXX) | Advanced | Notes |
|---|---|---|
| Vagrant Provisioner | [Demo-tasks v0.1.23] | Dropdown, same as standalone server |
| Hostname (Should match new ID)* | [demo-2.STARTcloud.com] | We are looking for a way to extract this from the ID file |
| Existing Domino server name to join with* | [demo.STARTcloud.com] | Needs to match the server used to create the ID fie below |
| Existing server IP address (optional) | [1.2.3.4] | For our local testing, the private IP address will be required, since DNS would not be setup for the other SHI instance. For customers, this should generally not be needed |
| New server ID file password (optional) | [password] | |
| New server ID file | [Locate] | File Chooser. You will need to generate this based on a local server. I'll send more instructions for this later. |
| Roles & Installation Files * | [Manage] | Same as standalone server |
Some things that are intentionally missing:
- Organizational Certifier - this is determined by the provided Server ID file. Also note that Hostname is technically not the server name here, unless the use sets it properly to match.
- Computed name (FQDN) - Since we don't have the Organizational Certifier, we can't compute this.
- Your Existing Notes Safe ID - The user should already be cross-certified against the domain
Some notes on getting the new server information from the ID file:
@JustinProminic pointed me to some code based on Registration.switchToID. This seems to work, but it needs to run as a Java application in a Notes or Domino environment. Some problems:
- Running it locally would require a Java 8 installation and configured Notes client.
- Running with a local Notes client has been broken for me since Notes 12, and it has never worked reliably
- We could theoreticaly run this on an existing SHI instance, but this seems impractical - the user would need to create standalone instance (if they hadn't already) just to get the name for an additional instance.
- We could send this to a Domino server to extract the required information, but sending the ID file to another server is a security concern.
It looks like it might be possible to parse the server name as text from the ID file. Opening the file with an editor, I see a lot of binary characters, but I can also spot plain text values with the server name and organization, in the format CN=demo-2.startcloud.com/O=DSP. I'm not sure how reliably we could parse this, but it is something we could experiment with.
@MarkProminic @JustinProminic @JoelProminic before I jump into this rabbit hole of implementation it would be good if we could officially release 0.1.23. Changes in SHI are waiting now for at least month or more to be used. Please consider that step first.