CVS log for loncom/auth/lonauth.pm

Up to [LON-CAPA] / loncom / auth

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

- For 2.11.4 (modified)
  Include changes in 1.121.2.27 (modified).

- If Remote Control is set to be used for current user, don't launch it if
  server is a loadbalancer, and session will be switched elsewhere immediately.

- For 2.11.4 (modified)
  Include changes in 1.149, 1.150, 1.151, 1.152, 1.158, 1.179

- 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.178

- Support access to specific LON-CAPA message after login in cases where a
  LON-CAPA loadbalancer node is used as the portal for a domain.

- For 2.11.4 (modified)
  Include changes in 1.177 (modified).

- Dual SSO and non-SSO login from /adm/login
  - Display of domain configuration for each server split into two tables
    so input textboxes can be longer.
  - "Pop-up if iframe" (Y/N) item added.  If Y, when login page is in an
    iframe, SSO log-in dialog will be displayed in a new window, i.e.,
    not within the iframe, e.g., to satisfy sameorigin requirement in
    x-frame-options in header sent by SSO server.

- For 2.11.4 (modified)
  Include changes in 1.174, 1.175, 1.176

- 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
  - Set request.linkprotuser in %env for students accessing deep-linked items
    with LTI link protection which includes username from other LMS.
  - Set "only_body" for intermediate pages shown while session is being set up
    for LTI link-protected access.
  - Provide appropriate feedback when a deep link is followed but the user
    only has a future and/or expired role in the target course.

- 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.

- Bug 6754 LON-CAPA as LTI Provider
  Escape any single quotes in destination URL to avoid javascript errors.

- For 2.11
  Include a single change from changes in rev. 1.140

- For 2.11.4 (modified)
  Include changes in 1.172

- For 2.11
  Backport 1.172

- Domain configuration to allow authentication of an alternate username, if
  username entered differs from real username in a predictable way,
  e.g., username entered in log-in page was email address (userid@example.tld)
  instead of just userid.

- For 2.11.4 (modified)
  Disallow launch of Remote Control for access via deep-link

- For 2.11.4 (modified)
  Include changes in 1.164, 1.165, 1.166, 1.167, 1.168 (part), 1.169 (part)
  Reverse part of change in rev. 1.121.2.23

- For 2.11
  Backport 1.170 (part) omitted in rev. 1.121.2.22.

- For 2.11
  - Include changes in 1.169 omitted from backport in 1.121.2.22.
  - Remove change from 1.168 included in 1.121.2.22 for tiny URLs (not part
    of 2.11).

- For 2.11
  Backport 1.163, 1.168 (part), 1.169 (part) 1.170

- Bug 6754
  - When log-in fails for a user with authentication set to lti: let user
    know they should launch LON-CAPA session via a different CMS.

- Expire any existing public cookie (and session) when establishing a session
  for a migrated user.

- 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.

- Use token to store role, symb, linkprot, and/or linkkey when dual log-in
  page to support SSO (Shibboleth) and non-SSO is in use, and for "log in
  again" retry link for failed login, instead of using query string directly.
- When digest is used by tmpput handler in lond to generate an id, only use
  id which does not already exist in LON-CAPA's tmp directory.

- 0 is a valid linkkey.

- Bug 6907
  - Deep-linking when user has an existing LON-CAPA session, need to support
    case where role change is not needed, but course session update needed to
    enforce link protection (lti-based or key-based access control).

- Typo in rev. 1.164

- Bug 6907 Content in a course can be set to be deep-link only.
  Enforce link protection for lti-based or key-based access control.

- Bug 6914.
  Replace hostname with alias when creating absolute URLs, if alias in use.

- For 2.11
  Backport 1.162

- 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.160, 1.161

- For non-SSO login on a balancer node, check for balancer cookie in lonauth.pm
  after login credentials validated. (Same as lonacc::sso_login for SSO login).
- Not all calls to check_loadbalancing() require determination of a server
  to which to offload, even when $is_balancer is true.

- Send HTTP header when displaying "no server available to host" page.

- For 2.11
  Backport 1.159

- Add domain configuration to offload users from other institutions, on next
  access (after recording any submission to a problem).
- Switching user session to a different server can jump to the same resource
  currently being viewed when encrypturl is in effect.

- For 2.11
  Backport 1.143, 1.154

- For 2.11
  Backport 1.144, 1.145, 1.146, 1.147, 1.148

- Include lti.login in form vars when new course needs to be created for
  instructor launch from LTI Consumer when URL is /adm/lti

- Bug 6400
  - Enforce access restrictions for content which is deeplink-only (users
    with "advanced priv for current role are exempt).
  - Support "key" link type in deeplink parameter (requested link must either
    be sent with linkkey as element in POSTed data, or with linkkey in query
    string).  Corresponding value must match key set in deeplink parameter.

- Bug 6400 Deep-linking
  - URLs like /adm/lti/tiny/domain/uniqueID can be used to restrict use of
    deep links to access from another LTI-enabled application (no user data
    passed in this context).

- Bug 6400. Preserve deep-link context, when prompting to log-in again
  after failed authentication.

- Use 'secure' attribute for session cookie on servers using Apache/SSL.

- Bug 6754 LON-CAPA as LTI Provider
  - If LTI Consumer does not provide 'launch_presentation_document_target'
    set $env{'request.lti.target'} to iframe, if LON-CAPA display in iframe.

- Bug 6754 LON-CAPA as LTI Provider
  - Creation of new LON-CAPA course available from an LTI Consumer.

- Bug 6754 LON-CAPA as LTI Provider
  - Simplified display when initializing LON-CAPA session after LTI launch.

- 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.

- Bug 6754 LON-CAPA as LTI Provider
  - Creation of new LON-CAPA user account available from an LTI Consumer.
  - Creation of new LON-CAPA course available from an LTI Consumer.
  - Self-enrollment in a LON-CAPA course available from an LTI Consumer.

- Bug 876.
 - Session hosting server and target user's home server must have the same
   "internet domain".

- Bug 876 for multi-domain servers.
  - Update documentation.

- Bug 876 for multi-domain servers.
  - Session hosting server and user's home server must have the same "internet
    domain".

- Bug 876 for multi-domain servers.

- Remove "use" calls no longer needed, as DES decryption now uses
  loncommon::des_decrypt().

- For 2.11
  - Backport 1.142

- Use 'secure' attribute for session cookie on servers using Apache/SSL.

- cookie protection

- For 2.11
  - Backport 1.141

- Domain Configuration for dedicated load balancer includes option to
  permit "Hosting on balancer itself".
- If balancer has lowest load, it will host the user session for a user
  logging in.

- For 2.11
  - Backport 1.139 (part)

- Bug 6808. New course container -- "Placement" for Placement Tests.
  Work in progress.

- Bug 5679

- Reinstate changes in 1.135 which were removed in 1.136

- For 2.11
  - Backport 1.137

- Eliminate 404 errors because of malformed urls such as /adm/adm/navmaps
  when user reloads a previously displayed LON-CAPA page in a browser where
  the session cookie has expired or been deleted.

Disabled encryption and decryption of user's password for login, if the
login server uses https. Otherwise encryption and decryption stay enabled.

For 2.11
 - Backport 1.135

Bug 6675
- Changed client IP address when load balancing:
  Support option to host on Load Balancer itself, after re-authentication.

- For 2.11
  - Backport 1.134

- coding style
  - return from subroutines.

- For 2.11
  - Backport 1.133

- Typo.

- For 2.11
  - Backport 1.132

Improved and consistent navigation and layout by using confirm_success and actionbox for failed login screen

- For 2.11
  - Backport 1.130, 1.131.

- Preserve requested role and/or symb from query string when switching user
  session from load balancer server.

- Remove superfluous ampersands.
- Remove som trailing whitespace.

- For 2.11
  - Backport 1.128, 1.129

- Validation.

- generate xhtml that satisifies w3c validation in cases where log-in failed.
- loncommon::font_settings() takes an optional argument -- a reference to a HASH
  from which browser support for unicode and mathml can be extracted, in case
  where user is unauthenticated.

- For 2.11
  - Backport 1.127

- Bug 6675
- Case where $env{'REMOTE_ADDR'} as reported to server selected to host
  user session, is different from $env{'REMOTE_ADDR'} as reported to
  server which handled original authentication request.
  - Domain configuration for a load balancing server can be set to one of
    the following, if an IP mismatch is detected by /adm/migrateuser
    during credentials checking after redirect via /adm/switchserver
    (i) Session will be hosted on Load Balancer
    (ii) Session will be hosted on offload server
    for each of (a) SSO users from load balancer's domain, (b) non-SSO users
  - Setting to host on load balancer will be ignored if switch server was called
    by an author or co-author switching to server housing the authoring space.

- For 2.11
  - Backport 1.126

Correct and improve error message:
- Internationalization: Do not translate already translated phrases.
- XHTML/Style: adjust tags to error page wrapper - <h1> not allowed within <p>.

- For 2.11
  - Backport 1.125.

- Fix typo in rev. 1.121.

- For 2.11
  - Backport 1.124.

- URLs beginning uploaded/ need to begin /uploaded/ when used as destinationurl.

- For 2.11
  - Backport 1.122, 1.123.

- Use custom log-in help page if defined for user's domain (or default domain
  if no user domain).

- Move &loginhelpdisplay() from lonlogin.pm to lonauth.pm to facilitate reuse.
- Log-in help page configuration moved from helpsettings to login section in
  Domain configuration interface.
- Add ability to upload different help files for the different supported languages.
- Link to log-in help page depends on user's browser language preferences.

- For 2.11.
  - Remote Control retained in 2.11.
  - Reverse changes in lonauth.pm rev 1.102, 1.104.
  - reverse changes in lonlogout.pm rev 1.38, 1.39, 1.40, 1.41.

changed <h1> to <p class='LC_error/warning/info'> where a headline is misplaced

- Customization for MITrelate
  - Backport 1.111.
  - Fix refs -- cancreate is an array ref; form is a HASH ref.
  - Pass domain description as additional arg in calls to &create_account()

- Customization for MITrelate.
  - Similar changes to rev 1.101.10.1 for GCI_3.

- use lonDocRoot perlvar in place of static string: '/home/httpd/html'.

- Backport 1.112.

- Backport 1.119, and one line from 1.109, not included in earlier 1.101.8.4 (backport).

- Use createaccount::get_creation_controls() to determine self-creation
  configuration if authentication results in: "no_account_on_host".
  - Consistent behavior for "New User?" link and log-in via standard log-in
    page for users authenticated by institutional log-in (kerberos or localauth)
    where domain has set rules for self-creation of accounts, based on
    institutional status.

- Backport 1.114, 1.115, 1.116, 1.118.

 - &lonnet::choose_server() returns an array.

- Bug 6371.
  - Use of lonBalancer in Apache config file superceded by setting
    loadbalancing in domain configuration.
  - More granularity available in load balancing:
     - Rules can be defined for users in domain, based on institutional
       affiliation (e.g., Faculty, Staff, Student etc.).
     - Rules for advanced user or author trump rules based on affiliation
     - Rules can also be set for users from other domain hosted by
       institution (i.e., multi-domain server set-ups)
     - Rules can also be set for users from other institutions.

 - &lonnet::choose_server() returns an array.

- If server is configured to deny hosting of sessions for user's domain,
  attempt to switch session to least loaded server in user's domain.
- Display message if no server available to host session.

- Check for "no_such_host" response.

- Backport 1.113.

- Bug 6472.
 -  Replace use of &lonnet::choose_server() with &lonnet::spareserver() as in
    lonnet.pm rev 1.1083 (and later) a check hosting is allowed is included.

- Remove HTML tags from phrases to translate.

- Bug 5932. Roles Screen usability improvements.
  No "Check for new roles" button immediately after log-in.

- Backport 1.110.

- Coding style for readability.
  - Move return OK to main handler.
  - Need return OK after $r->internal_redirect in main handler.
  - &check_can_host() returns 0 or 1 (1 if canhost).

- Customization for GCI_3.
  Eliminate case sensitivity in usernames except for existing
  users with usernames which include upper case characters.

- Backport 1.109.

- Offloading from a busy server delayed until after authentication so
  user's domain is available when determining which less loaded server
  will host (check that hosting is allowed).

- Backport 1.108.

- lonnet::get_internet_names() returns a reference to an array.

- Backport 1.105, 1.106, 1.107.

 &choose_server() moved from lonauth.pm to lonnet.pm to facilitate reuse.

- Control hosting of user sessions.
  - To accommodate multi-domain library servers, use internet domain names (e.g., msu.edu)
    instead of LON-CAPA domains in interface DC uses to set options for session hosting.

  - Provide mechanism to retrieve lonHostID for a hostname, so we can tell which
    domain determines session hosting config for external users on a multi-domain
    machine.

  - New routines in lonnet.pm:
     &get_server_homeID()  -- gets lonHostID for a hostname
     &internet_dom() -- gets internet domain name for a LON-CAPA Host ID
     &get_internet_names() -- gets internet domain names for all domains
                              for a server given one of the LC host IDs for the server.

   - New file in /home/httpd/lonTabs:
     - serverhomeIDs.tab (populated by loncron). : paired hostname:lonHostID

   - New subroutine in loncron: &write_serverhomeIDs() -- populates serverhomeIDs.tab
   - New subroutine in lond: &server_homeID_handler() -- returns LON-CAPA Host ID of server
   - New scalar in lond: $clienthomedom -- set to domain of LON-CAPA Host ID of client
   - New subroutine in domainprefs.pm: &build_location_hashes()
       -- used to set up options for session hosting as internet domain names
           - where two names (e.g., msu.edu, loncapa.org) are controlled by the same
             institution these will receive a single checkbox.

- Following the switch to 2.10, domains may prefer that their users do not have sessions hosted on older versions of LON-CAPA.
- Domain Coordinators can control:
  (a) where their users may have sessions hosted (by domain and/or LON-CAPA version).
  (b) which other domains will have user sessions hosted on servers in the domain.

- Backport 1.103.

- Backport 1.103.

In process of removing remote control, remote navmap and different icon modes code
- removed no_inline_link argument from loncommon::start_page, loncommon::bodytag
- removed subs
    o loncommon::head: it wasn't used
    o loncommon::endheadtag: functionality now covered by loncommon::headtag
    o lonmenu::registerurl: functionality moved to loncommon::headtag, because it was the only function that called registerurl
- removed remote control related translations in de.pm
- refactoring and cleanup

- If user is already logged in, load user's %env so primary_menu links are shown for user.
- Don't display "login problems" link, if user is already logged in,
  as it doesn't make sense here.

In process of removing remote control, remote navmap and different icon modes code
Also some minor refactoring.

- Revert changes in 1.98 and 1.99 as they are not in 2.9.X.

- Bug 3987.
- Destination URL and Symb supplied in query string to log-in page, used to load page after appropriate role selection.

- Bug 3987. Deep linking.
- Include role and symb in query string when calling log-in page.
- Role is automatically selected and resource is displayed (assuming user actually has the role, and its active, and symb is valid).

Added breadcrumbs to successful login forwarding page

Redesign: no separate accessibility interface, cleaning up a bit

Edited Exit, Logout, log in, log out in eng/ger for consistent wording.

Ties up process.

Optimizations for authentication fail:
- Added 1 second break as a brute force counteraction
- Added warning style to failed messages

Move duplicate code in lonauth.pm and createaccount.pm which handles result from createaccount::username_check() into username_check() for both log-in ID and SSO cases.
- additional args ($contact_name $sso_logout) passed to &username_check for SSO case.
- Page for user information data table customized based on availability of data fields, and whther data can be entered (according to $rowcount and $editable args returned from &loncreateuser::personal_data_display().
 - If no values are available or editable don't display table.
 - If only non-editable values are available - display table with appropriate message.
 - If one or more editable values - display table with appropriate message.
If username check reports errors (e.g., 'username' not in institutional database, or 'authtoken' - authtoken could not be set) - display appropriate error reports.

User account creation cases:
- Updating args sent to &createaccount::username_check() to include $lonhost
   and $contact_email.
- Set contact e-mail address to the first address in the comma-separated list
   from loncommon::build_recipient_list().
- Adding some header lines and wrapping some messages in <span>s for LC_warning
   or LC_error.
- Adding advice on e-mail contacts where createaccount::username_check() returns
   checkfail for authenticated user, where account creation is permitted.

Localization:
- Added missing &mt() calls
- Changed "Problems?" to "Login problems?" to avoid translation conflicts

- If a user successfully authenticates via SSO, but a LON-CAPA account is lacking for the username used to authenticate, offer the possibility of creating an account, if selfcreation is allowed for the 'sso' auth type.
- selfcreation auth types are now stored as an array, instead of a single-valued scalar.

- Authentication will be attempted for users attempting to log-in with usernames for which there is no user account, if account creation is permitted for the 'login' type.
- If supplied credentials are authenticated, the user will be able to create an account in the domain. (Requires default authentication in the domain to be Kerberos or localauth -- see lond 1.396).

- use the lonnet session validation mechanism

- translate failure messages

- swithc to using helper cleaing functions and helper matchi re

- add explict ability for robot logins that don't kill actual user sessions

- move the session start up into loncommon.pm

- backport 1.84

- if no form sent don't ISE

- change sesion env into a .db file
  (simplifies the appenv/delenv process)

- user environment gets it's keys prefixed

- optimizing the login for users (fewer redirects occur) also if the user
  is going to be load balanced don't fire the remote up on the initial
  server

- migration wants to add in some env vars

- make use of new hash interface
- user environment needs environment. prefix
- esacpe user info when first inserted into env

- eliminate use of Apache::File
- session environment should be escaped

- batter screen and internal error message for the case when server can't find itself

- don't show th inline toggle link on the login/out screens

- handling timezones correctly

- start_page

- default to no remote control BUG#4337

Guy is so right: much better display of time zone.

Display timezone for absolute dates and times.

- 'switch server' now really does

- support multiple public users at a time (100) BUG#2573

- BUG#2573 can't do randomlabel/imageresponse/reactionresponse/organicresponse etc as 'public' resources,
   - public users on first access get a Cookie and a skeleton of a session environment now

Bug #2616: password can have 45 characters now

- ENV -> env

- ttm can now be forced on, which means Hi XML, what you mean we really have to be xml now?
   - roles screen with no roles doesn't barf in xml mode
   - viewing a homework problem with an inline remote and no selected roles doesn't baf
   - pref screen to change back to something else doesn't barf

- no guarentees about anything else, not that the remote control in particular is non functional

- add continue link to lonauth.pm BUG#2665

- let user know what we are doing when we are loading the remote, also provide a link to disable the remote control, should addres BUG#3572 and related

- We were emitting 2 <html> tags

Bug #876: logging in as somebody else.
Username: (realname):(su-name)

Bug #2403: document encoding on welcome page.

Bug #2357: Multiple logins from same host detected, even for round-robin IP
(because for example s2.lite.msu.edu-cookie does not get sent to
msu.lon-capa.org/adm/login).

Bug #2060: IE does not update URL field, points to
/adm/remote?action=collapse on re-login.

Internationalize Welcome screen.

Setting content language in headers.

Continued work on localization.

Translation files go into

loncom/localize/localize

as

de.pm
pt.pm

etc. Rest should be automagic.

Also have login handlers detect re-reouting.

Better safe than sorry.

Passing of parameters to locate local client-side files.

Rewinding changes on window registration.
Attempting to overcome JavaScript security by using POST to change window
location.

Cleaning up after bug #1178 - keep track of WHICH window is closed
Bug #1472 - should not go "haywire" anymore when closing Remote while
clientwindow shows external resource

Slow steps toward Bug #1472 - closing remote while being at external site

- Perl 5.80 + mod_perl 2.0 + APache 2.0  really want the 0 in there

New environment variable $ENV{'request.role.adv'} to check if the *current*
role is advanced.

Handle login without Remote.

I'm sorry, but this was driving me nuts:
"Please login again" is now "Please log in again".

Created loncommon::decode_user_agent() subroutine with code removed from
lonauth.pm.  The code was modified to not require $r be passed along
ad nauseum.

Created lonhtmlcommon::javascript_nothing which returns an appropriate value
of nothing for use as the first parameter for window.open.  Most notably,
IE on macs get a different version, "'javascript:void(0);'", than everyone
one else, "''".  Of course IE on PC appearantly used to require the former
but now requires the latter.

lonmenu.pm and lonspreadsheet.pm were modified to use javascript_nothing.
lonauth was modified to use decode_user_agent.

Fixes possible security problem.

Bug #1285
loncron cleans login tokens after a day.
* lonauth now give better error messages
* lonlogin refreshes the login page after a day
  (so the "expired" error should never happen anyway)
* loginproblems was adapted

$ENV{'remote_host'} made no sense
userstatus counts domains now

- apparently late night coding brings out the whitespace anal-retentive Guy

* Additional browser information
* Accessibility options get stored in environment for "remember"

Switch off applets (if it was up to me, this would be default)

Transfer login screen accessibility choices to session environment

Relay interface information to environment

best wishes to all.

Attempt to work on bug #1205 by changing the timing of events at login for the
remote. Also, trying to isolate remote-related code into lonmenu.pm so that
alternative remotes/navigation become easier to implement later.

Help link with common login problems on login and welcome screens.
Unfortunately, we cannot use the cool help system here, since it will
not work when pop-up ad filters are installed.

- adding code for setting the browser.unicode ENV
- extended lonBrowseDet, adding a new field, which is the version of the
  browser wihch needs -u1 rather than -u0

- I have a couple of dreams
1) to never see a call to reply outside of lonnet.pm
2) to see the use of esace/unescape minimized
3) world peace


- Anyway this change has the side effect of fixing the problems with %20
 etc appearing in the middle of names.

(Don't be afraid of lonnet::dump/get/put etc, they try to do it right.)

For bug #54.
Needed to exclude linux/unix from automatic resizing and repositioning of
browser windows because of virtual desktop sizes (desktopsize!=screensize).
Looks like this also fixed bug 468 - "misbehavior" was apparently
(not confirmed) due to overlap of windows.

Take care of a javascript warning (undeclared variable) as part of cleanup
needed for BUG 385.

Changes to lonmenu::rawconfig() to not display the 'cstr' button if you do
not have privleges on the current server.

Set browser type in environment so it works already at first login.

GPL

making backwards compatible with old Crypt::DES

fixing targeting of DES function

Bounces to roles screen rather than welcome

setting a wider time limit to accomodate slow connections
mixed with slow servers

Does not go to "critical" if there had never been a critical message

Detects critical messages

bug fix to stop remote control timeout

For new Remote Control - initialization

- flocks the enviroment

Glob free cleaning up of old session profiles (to avoid shell calls)

Info for lonnet::allowed added early into the request cycle

Clears out role information, sets role to "cummulative"

Checks for critical messages

Does not log you out right after login from /adm/logout

The menu does (should) not  go into the autologout/forbidden cycle anymore

Load environment.db into session environment

lond propath now works for less than 3 char username
lonauth now recognizes Windows machines

Fixed firsturl bug with special character &

Login mechanism now uses encryption
lond has new routines for temporary entries tmpget, tmpput

Updates. Implement roles control on browsing and menu.

Restored direct jump to URL

Authentication changes - incorporated into environment

Roles have starting and end time
Bug fixes after replication shift
New login screen
Authenticator routes to roles screen
Form variables are transfered to environment (not tested)

lonauth imports roles into environment

Putting environment variables into session profile
Reading environment variables from session profile
Not tested yet

LON-CAPA Communication Module

Initial revision