Sign In¶
The BO console and Meta Query on the web sign you in with your MetaMiner user, and share one web session per browser.
How it works¶
Both apps use the MetaMiner users and permissions you manage in the MetaMiner Administrator (MMA). The MetaMiner Server (MMS) checks the password and the permission, then issues a web session. The session belongs to the browser: signing in on the BO console also opens Meta Query in the same browser, and signing out of one signs out of both. Each app still checks its own permission.
| App | Who can sign in |
|---|---|
| BO console | MetaMiner users with the MMC permission on at least one enabled BusinessObjects environment, and MMDB administrators |
| Meta Query on the web | MetaMiner users with the Tab: Meta Query permission on at least one enabled environment, and MMDB administrators |
Sign-in requires MetaMiner user-based security. Turn it on before you enable the BO console: see User-Based Security and Users and Roles.
Use HTTPS
From another computer, the sign-in box works over HTTPS. Turn on MMS SSL so that passwords and sessions travel encrypted: see SSL Overview. On the MMS machine itself you can also sign in over http://localhost.
BO console sign-in modes¶
Choose the mode on the MMA Preferences > Settings... > WebApps page, field Sign-in: (server property web.bo.login).
| Mode | Default | What users see |
|---|---|---|
| Required | yes | A sign-in box before any page. Every page and data request needs the session; when it ends the box comes back with "Your session has ended; sign in again." |
| Optional | Pages open without signing in. A Sign in button in the top bar offers it, and the session then also opens the MetaQuery module. | |
| Off (no sign-in) | No sign-in at all. Anyone who can reach the server can use the console. |
Keep Required unless the MMS port is reachable only by administrators. When MetaMiner user-based security is off, the console behaves as Off whatever the setting says.
Pages that change BusinessObjects ask again
Applying server configuration changes, saving notifications and running jobs always ask for your MetaMiner user and password in the page, in every mode. The MMS checks them and your permission for that action on each environment involved (for example Change Server Configuration for server settings). See Permissions Reference.
Sign in to the BO console¶
- Open
https://<mms-host>:<port>/web/bo/, or File > Launch BO Console... in the MetaMiner Client (MMC). - In the BusinessObjects console box, enter your MetaMiner user and Password.
- Click Sign in.
Result: the console opens and your user name and a Sign out button appear in the top bar.
Image of the BO console sign-in box: MetaMiner logo, 'BusinessObjects console', MetaMiner user and Password fields, Sign in button and the note 'Sign in with the MetaMiner user you use in the MetaMiner client'
../images/web-console/bo-console-sign-in.png
Meta Query sign-in¶
- Open
https://<mms-host>:<port>/web/metaquery/, or File > Launch MetaQuery Web... in the MMC. - Enter your MetaMiner user and Password and click Sign in.
- If anonymous use is allowed, you can click Continue without signing in instead.
Image of the MetaQuery sign-in box with MetaMiner user, Password, Sign in, and the Continue without signing in button shown because anonymous use is allowed
../images/web-console/metaquery-sign-in.png
The sign-in box tells you when it cannot be used: "The web console is turned off on this MetaMiner server." (Meta Query switch off) or "User security is off on this MetaMiner server; sign-in is unavailable."
Tiers¶
Your tier decides the limits that apply to your queries.
| Tier | Who | Notes |
|---|---|---|
| Users | Signed-in users with Tab: Meta Query | History, saved queries and workspace are kept on the server |
| MMDB administrators | Signed-in MMDB administrators | Higher limits; see every user's running queries and history |
| Anonymous | Anyone, when Allow anonymous use is on | Lowest limits; nothing is saved on the server; no e-mail; sees shared saved queries only |
Limits per tier: Meta Query on the Web.
Session expiry¶
| Rule | Default | Server property |
|---|---|---|
| Idle timeout: the session ends after this many minutes without a request | 60 minutes | web.metaquery.session.idle.min |
| Absolute lifetime: the session ends this many hours after sign-in, active or not | 12 hours | web.metaquery.session.absolute.hours |
The same rules apply to the BO console session. A session also ends when the user is disabled or changes the password, and when the user signs out in another tab of the same browser ("You signed out in another window.").
Troubleshooting¶
"Sign-in needs HTTPS" in the top bar, or the sign-in box explains that a password would cross the network unencrypted
You opened the page over plain HTTP from another computer. Open it with https:// after turning on MMS SSL, or use a browser on the MMS machine.
"Too many sign-in attempts from this address; wait a minute."
Repeated sign-in attempts from one address are limited per minute. Wait a minute and try again with the right password.
The password is correct but sign-in is refused
Check that the user is enabled and has the permission listed above on at least one enabled environment. A disabled, locked or expired MetaMiner user gets the same answer as a wrong password.
The BO console signs me in but the MetaQuery module stays hidden
Your user lacks Tab: Meta Query, or Meta Query on the web is turned off.