Skip to contents

authorize() uses stored values to authorize a browsing session in Banner.

Usage

authorize(reset = FALSE)

Arguments

reset

Indicates previous values should be ignored and overwritten.

Value

An rvest session

On first run

The first time authorize() is run, it will request and store key values for logging into Banner, including the institutional URL, the current term, and others. The user will also be prompted to store a login username and password in the system keychain.

First-run details requested

Values requested at this stage include the following:

  1. The base url of a Banner instance, used when navigating by web browser

  2. The current term used internally by Banner. This might take the form of something like "202420" for the second semester of the 2023-2024 academic year.

  3. For the login page, any url details added to the base url. Once the base url has been entered, a value is suggested.

  4. For the course rosters page, any url details added to the base url. Once the base url has been entered, a value is suggested.

  5. For the attendance rosters page, any url details added to the base url. Once the base url has been entered, a value is suggested.

  6. The username used to log in to Banner.

  7. The password used to log in to Banner.

Security considerations

The first five values are not sensitive, but the last two certainly are. The first five are stored as environmental variables. Meanwhile, the username and password are treated with heightened security, manged using rstudioapi::askForSecret() and, potentially, stored by it in the system keyring.

Examples

if (FALSE) {
  my_session <- authorize()
}