Sign in to the Oda web app

DataMind Oda signs a browser in to its web app in a single visit: there is no password to enter and no account to create. This page is the reference for that sign-in: what the printed address carries, how a browser keeps its sign-in, and how the sign-in ends. To start the web app, see Oda in the browser; to work in it, see The Oda web app.

Signing a browser in

1. Start the web app. DataMind Oda prints the address to open; Oda in the browser covers starting it.
2. Open that address in the browser you want to use, exactly as printed. The visit signs this browser in and the app loads.
3. Return later from the same browser, and the app opens directly.

The printed address carries a one-time sign-in token, and opening exactly that address is the whole sign-in: the token is exchanged for this browser's sign-in, and the page settles on the plain address without the token. The token is read only from the address as printed, and a browser that already holds a sign-in does not need it again.

A browser that has not signed in yet gets a plain line instead of the app: Sign-in required; reopen the address the server printed when it started. Open the address from the latest start of the web app; if you no longer have it, start the web app again and use the address it prints.

How a browser keeps the sign-in

• It is kept by the browser, as a cookie for the web app's address. It survives closing the browser and restarting the web app.
• It belongs to the exact address that issued it: the same name and port. A sign-in at one address does not cover another.
• Each browser keeps its own sign-in: signing in one browser does not sign another in. Open the printed address in each browser you want to use.
• The web app prints a fresh token every time it starts, for signing in browsers that have none; a sign-in a browser already holds stays valid until it expires.
• It lasts 30 days by default, counted from when the browser signed in. After it passes, that browser is asked for the printed address again. Connection settings and defaults covers changing the lifetime.

Ending the sign-in

The interface has no sign-out: nothing in the page ends a browser's sign-in. To end one, clear the web app's saved data in that browser, including the cookie for its address; the next visit from that browser asks for the printed address again, and the other browsers keep their own sign-ins.

Questions, answered

What is the token in the printed address?

It is the sign-in for one start of the web app. Opening the address exactly as printed exchanges it for this browser's sign-in, and the page settles on the plain address without the token. The token is read only from the printed address, exactly as it is; it cannot sign a browser in from anywhere else. A browser that already holds a sign-in does not need it again.

What does the page show in a browser that has not signed in?

Instead of the app, a plain line: Sign-in required; reopen the address the server printed when it started. Opening the plain address does not sign a browser in: reopen the exact address from the latest start of the web app, or start the web app again and use the address it prints. The other messages this path can show are listed in Connection and upload messages.

Why does a changed address ask for the sign-in again?

The sign-in is kept for the exact address that issued it: the same name and port. If the web app now serves another address, for example after a restart on a different port, the sign-in a browser holds does not cover it; open the newly printed address to sign in again. A restart on the same address keeps the sign-in. This is separate from the check of which addresses may reach the interface; Local access and trusted hosts covers that.

Does the sign-in expire on its own?

Yes. A sign-in lasts 30 days by default, counted from when the browser signed in; after it passes, that browser is asked for the printed address again. Your installation can set a different lifetime, covered in Connection settings and defaults.

How do I end a browser's sign-in?

There is no sign-out inside the interface. Clear the web app's saved data in that browser, including the cookie for its address; the next visit from that browser asks for the printed address again, and the other browsers are not affected.

Can I end every sign-in at once?

Not from inside the interface. Oda keeps one record on this computer behind the browser sign-ins; replacing that record and restarting the web app ends them all together, so every browser signs in again from the newest printed address. This is a step for your DataMind OS administrator.

Is this the same as signing in to DataMind?

No. This sign-in belongs to the web app: it decides which browsers may use it on this computer, it is kept by the browser, and nothing is typed. Your DataMind account is separate: it is what DataMind Oda itself signs in to for models, company data and updates. Its sign-in is set up in Install and sign in, and the messages it can show are listed in Troubleshooting.