Fixes #1598 by adding a regular expression pattern property for the web connector.
I also noticed the auth cookie's Path was kept to the default value. This made me consider the following possibilities:
change the Path to / - this ensures consistent access, but prevents having different user identifiers per connector
Change the Path to the connector path configured in TOCK Studio - this ensures the user identifier is scoped to a single connector, but it becomes incompatible with reverse proxies and other route-rewriting middleware
Keep the current behaviour, but add a configuration option for a fixed path - this allows per-connector scoped user identifiers (although requiring sufficiently distinct connector paths), while allowing sharing when appropriate
I figured 3. was the most useful behaviour, but this could be a miscalculation. Feedback appreciated.
Fixes #1598 by adding a regular expression pattern property for the web connector.
I also noticed the auth cookie's
Path
was kept to the default value. This made me consider the following possibilities:Path
to/
- this ensures consistent access, but prevents having different user identifiers per connectorPath
to the connector path configured in TOCK Studio - this ensures the user identifier is scoped to a single connector, but it becomes incompatible with reverse proxies and other route-rewriting middlewareI figured 3. was the most useful behaviour, but this could be a miscalculation. Feedback appreciated.