Running report sets via URLs with authentication parameters

Sometimes you are required to give your user name and password before you can run report sets. Under this circumstance, if you want to avoid the login dialog in the web browser, use either of the following two parameters:

• jrs.authorization
  Tag of the HTTP query field jrs.authorization.

  Description: Loads the JRServlet and avoids the login dialog in web browsers.
  Format of the value of the HTTP query field: Base64-encoded (userID:password).
  Example:

  If the user ID and password are both set as admin, then the value of the HTTP query field is Base64-encoded("admin:admin")="YWRtaW46YWRtaW4=", and the URL will be as follows:

  http://localhost:8888/jrserver?jrs.cmd=jrs.get_subnodes&jrs.authorization=YWRtaW46YWRtaW4%3D.

  Note: The JRServlet does not check security when an HTTP request has no jrs.cmd in the HTTP query in the root path of the JRServlet, and also does not accept the jrs.authorization for the request http://localhost:8888/jrserver?jrs.authorization=YWRtaW46YWRtaW4%3D.

• jrs.auth_uid and jrs.auth_pwd
  Tags of HTTP query field: jrs.auth_uid and jrs.auth_pwd.

  Description: Loads the JRServlet and avoids the login dialog in web browsers.
  Format of the value of the HTTP query field: jrs.auth_uid=USER_ID, jrs.auth_pwd=PASSWORD.
  Example:

  If the user ID and password are both set as admin, the URL will be as follows:

  http://localhost:8888/jrserver?jrs.path=/SampleReports&jrs.cmd=jrs.get_subnodes&jrs.auth_uid=admin&jrs.auth_pwd=admin

  Note: The JRServlet does not check security when an HTTP request has no jrs.cmd in the HTTP query in the root path of the JRServlet, and also does not accept the jrs.auth_uid and jrs.auth_pwd for the request http://localhost:8888/jrserver?jrs.auth_uid=admin&jrs.auth_pwd=admin.