Search results

...uest are just forwarded to the middleware. In more advanced use-cases, the login request is forwarded to IDM of the customer and an OX session is created fr

...//documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (login module)]. * <code>session</code> - A session ID previously obtained from the login module.

* Open a webbrowser and login to the groupware web-interface

Once you have created these contexts, you should be able to login to OX GUI (if Database authentication Plugin is used) with username "contex

''Also, please note that all limit settings are set per login. They are not global, nor are they permanent; existing only for the duratio The limits per login are applied via the ''pam'' stack. See '''man pam''' and '''man pam_limits'

...ode> to enable autoconfig sending via email. PS: Have a fully working smtp login available like “noreply@yourdomain.tld” # Login to AppSuite. Click on Settings - Connect your device

...ry time load balancer sends them to a different node (i.e. on almost every login). This is also why the timestamps can't be updated automatically: a node do

# to 'user'. Possible values are 'login' (the user's individual mail login as

...s with both Dovecot Pro and OX App Suite as a component to protect against login/authentication abuse. OX Abuse Shield runs on a cluster of servers, and int

** Bugfix #29773 - Unable to login as webmail user after changing cPanel account name * Fixed Addon Domain handling (login to Open-Xchange was not working for email accounts in Addon Domains)

|Password encryption failed for login %1$s on server %2$s (user=%3$s, context=%4$s). |Password decryption failed for login %1$s on server %2$s (user=%3$s, context=%4$s).

When finished start your appsuite and login, add ''&customManifests=true'' to the url to load your plugin and reload th

* Open a webbrowser and login to the groupware web-interface

On the first login after the restart, all required database tables will be created. -->

...ssions that were bound to that machine were lost, i.e. the users needed to login again. With the distributed session storage, all sessions are backed by a d ...automatically start update tasks on a database schema when a user tries to login whose context lives on that schema. For installations beyond a certain size

...n, DB schema changes are executed. Finally, users are unlocked and able to login again. Schemas typically contain a few thousand users (if our recommended s

#:api.php?call=getupsellresources&login=$1 [L,QSA]

The login user name to be used for calls to the SharePoint service<br>

| <nowiki>Keypair to use for ssh login </nowiki> | <nowiki>Keypair to use for ssh login </nowiki>

| <nowiki>Keypair to use for ssh login </nowiki> | <nowiki>Keypair to use for ssh login </nowiki>