CVS log for loncom/lontrans.pm

Up to [LON-CAPA] / loncom

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

- For 2.11.4 (modified)
  Include changes in 1.41

- Bugs 6754 and 6907
  - Return of grades to launcher CMS supported for resources or folders
    accessed via LTI-mediated deep link.
  - Support option: "Encrypt stored consumer secrets defined in domain"
  - Signing of LTI payloads for roster retrieval, passback of grades,
    and callback to logput launcher CMS session all now occur on
    primary library server for course's domain.

- For 2.11.4 (modified)
  Include changes in 1.39, 1.40

- Bug 6907
  "Exit Tool" button available to logout a session launched via deep link
  and escape iframe and redirect (for LTI-protected link).

- Bug 6907
  For LTI-protected deep links in which username is included in launch payload
  compare username in payload with username for any existing LON-CAPA session
  in current web browser and expire old session, if different user.

- For 2.11.4 (modified)
  Include one line from changes in 1.18

- For 2.11.4 (modified)
  Include changes in 1.34 (part), 1.37 (part)

- For 2.11
  Backport 1.27, 1.28, 1.29, 1.30, 1.31, 1.32, 1.33, 1.34 (part),
           1.35, 1.36, 1.37 (part), 1.38

- Dual SSO and non-SSO login from /adm/login for use with additional SSO
  mechanisms besides Shibboleth.
  - Default is to use /adm/sso for "authentication" URL.
  - Different authentication URL can be set with lonOtherAuthenUrl perlvar.
  - Update documentation for lonshibauth.pm and lonshibacc.pm
  - Wording change for WAF/Proxy domain configuration
  - If Apache config contains lonSSOEmailOK set to 1, default removal
    of @ "internet domain" from username for SSO authenticated users in
    lonshibacc.pm is skipped.
  - &alias_shibboleth() routine in lonnet.pm renamed alias_sso().

- Bug 6907
  - Use of token to store linkprot or linkkey compatible with use of
    btoken and iptoken (for load balancing and IP change respectively).
  - Launching access from a deeplink, with its own ltoken and/or linkkey,
    for a user session originally launched from a different deeplink will
    update required session information.

- Bug 6914
  Domain configuration for WAF/Proxy includes Y/N option for use of alias in
  redirection to /adm/sso for server(s) supporting Shibboleth Single Sign On.

- Session information for user public:public does not need to be preserved when a user needs to be switched to/from hostname used for WAF/proxy.

- Bug 6914. Running LON-CAPA behind web application firewall/reverse proxy (WAF)
  - Requests for /adm/lti/* and /adm/launch/* should not be redirected to an
    alias (if in use).
  - Requests for /adm/dns/* from other nodes in the network do not require
    to an alias (if in use).

- Bug 6914
  If a LON-CAPA load balancer is a Shibboleth SP and WAF/Reverse Proxy in
  use, (SP excluded), escape part of css filename to avoid 404 when css is
  requested for /adm/switchserver.

- Bug 6914
  If a LON-CAPA server is a Shibboleth SP, requests to the SP are to the
  "official" hostname not the alias for consistency with lonshibauth.pm.

- Bug 6914
 - Check whether WAF proxy alias should be used when using switchserver.
 - Requests for /adm/dns/hosts and /adm/dns/domain from other nodes in the
   network do not require redirecting to an alias (if in use).

- Bug 6914
 - Update domain config UI to support settings documented in
   Domain_Configuration_WAF_Proxy.tex
 - Use /adm/migrateuser to handle redirects when user with a LON-CAPA session
   switches between access via VPN and not via VPN (and vice versa).

- Bug 6914. Consistent naming of domain configuration key: wafproxy.
  Rename exempt key in inner hash as 'vpnint', and add vpnext key to inner
  hash (required where VPN users will not use WAF, but other users will).

- Bug 6914. Support selective use of WAF/Reverse Proxy, e.g., VPN users
  connect directly (no WAF), whereas non-VPN users must connect via WAF.

- Retrieval of requestor's IP address centralized in lonnet::get_requestor_ip()
- Domain configuration to allow domain's LON-CAPA nodes to operate behind a
  WAF/Reverse Proxy using aliased hostname (CNAME).
- Web requests from other nodes bypass the WAF as their requests are made
  directly to the server hostname (A record); same for internal LON-CAPA
  connections for lonc -> lond.

- For 2.11
  Backport 1.26

- Accommodate Apache 2.4 updated to address CVE-2019-0220.
  Reverse piecemeal changes (lonwrapper.pm 1.72 & lonprintout.pm 1.670)
  with generalized solution using PerlTransHandler.

- Bug 6400 Tiny URL for deep-linking.
  - For user's with an existing active session URL translation of deep link
    (i.e., /tiny/$domain/$uniqkey) moved from PerlTransHandler (lontrans.pm)
    to lontiny.pm.
  - Checks made to see if course session needs updating, and if so,
    lonuserstate::readmap() is called for top-level map.

- Fix logic.

- Use internal_redirect to redirect to resource pointed to by a tiny URL, except
  when authenticated via LTI.

- Bug 6754 LON-CAPA as LTI Provider
  - LTI launch results in call to ltiauth, even if user has existing LON-CAPA
    session (role, course etc. will be updated).
  - LTI launch can be for a published .sequence

- Bug 6754 LON-CAPA as LTI Provider
  - LTI launch can be for a published .sequence or .page
  - LTI launch can be for a composite page.

- Bug 6754 LON-CAPA as LTI Provider
  - Original LTI launch of LON-CAPA is for a resource, a map, or an entire
    course, and display is for iframe, tab or window; retain this in %env.

- Display a listing of the folder's contents when deep-linking is to a
  folder not a resource.

- Bug 6400 Tiny URL for deep-linking.
  Requires Short::URL and String::CRC32 modules from CPAN. Dependency on
  perl-Short-URL needs to be added to LONCAPA-prerequisites.

- Bug 6754 LTI Integration: LON-CAPA as LTI Provider
  - Work in progress

- Support Apache 2.4 using $r->get_remote_host() from Apache2::compat().

- Use Server Name Indication (SNI) and SSL when replicating content from
  /raw/.
- Domain status screen has link to show status of LON-CAPA SSL certificates.
- "SSL" domain config for (a) "internal" LON-CAPA SSL connection to servers/VMs
  in other domain, (b) Replication of domain's resources to other domains.
- Replication can use name-based virtual hosts with SSL, with verification of
  client certificate (cert: /home/httpd/lonCerts/lonhostnamecert.pem, signed
  by LON-CAPA CA, with Common Name of internal-<server hostname>, same IP address
  as server hostname).

Saving my work on Bug #1320.

- more re fix ups

- ugh, ugly ass workaround for BUG#4948

&Apache::lonnet::unescape -> &unescape
&Apache::lonnet::escape -> &escape

- @ufile might not have a value

- multi-domain authors weren't getting CSTR buttons, BUG#3153

Simpler to get lonHostID from perlvar.

URI translation modified for requests for uploaded files.
Support added for requests for files in /raw/uploaded. Such requests are generated internally by lonnet::getfile() to request a file from the home server for a course.
URI translation to the appropriate file in /home/httpd/lonUsers/$cdom/$cnum. Will also do URI translation to the same path for files in /uploaded, IF request comes from a user session hosted on the home server for the course.  For sessions hosted on other servers, URI translation does not occur here, but in the PerlHeaderParserHandler phase (via lonuploadrep.pm).

- consoladating the 3 different &propath()s

- need to return something

Winning the commit war can be achieved by making minor changes to other
programmers code as well as your own.
Death to $dum1 & $dum2 !!!  Long live undef!

- so many half assed fixes for the fact that APache doesn't do proper evaluation of the ~ for non Unix based lon-capa users could have been avoided by doin this in the first place.

- Any way should make a god $r->filename for all users under all conditions, this ostensibly fixes BUG#812 (but maybe others)

Routines for file upload

Towards inter-server document transfer