version, doc, changelog for new release

CHANGELOG.md

@@ -3,6 +3,34 @@
 
 
 
+## [5.2.0] - 2023-05-30
+
+### Added
+
+-   `None` Nothing added
+
+### Changed
+
+-   `Enhancement` Added support for Proxy Authentication using user/pw. Support for having a proxy server ahead
+of Viya was added in version 4.5.0, and in this release, support for authenticating to that proxy with user/pw
+was added based upon a user request. This is documented in the HTTP section of the Configuration documentation.
+
+### Fixed
+
+-   `Fixed` A minor fix for a case where a unit test was producing a resource warning. I couldn't reproduce this,
+but the fix was trivial and it fixed the users case. This was for issue 543.
+
+-   `Fixed` A fix in the STDIO access method to explicitly use 'localhost' in the filename statement generated for
+dataframe2sasdata() instead of using blank hostname. This was causing an issue for a user with multiple network
+adapters and an unusual configuration. Explicitly using localhost is the correct path for this since SAS and Python
+are on the same machine, so using the loopback adapter is the right choice.
+
+### Removed
+
+-   `None` Nothing removed
+
+
+
 ## [5.1.2] - 2023-04-28
 
 ### Added

saspy/doc/source/configuration.rst

@@ -950,6 +950,17 @@ them here, as they are mutually exclusive. You use only one of the various means
 Again, only use one of these and don't mix using config keys from more than one for a given connection.
 
 
+Authenticating to a Proxy server:
+
+Support for having Viya behind a proxy server was added in version 4.5.0. The `proxy` key is used to provide the host and port.
+I had a request from a customer to add support for authenticating to the proxy server itself, before then authenticating to Viya.
+Support for this was added in version 5.2.0; for authenticating to the proxy via user/pw. There are new configuration definition
+keys to support this; `proxy_authkey`, `proxy_user` and `proxy_pw`. To use this you must specify `proxy_authkey` or `proxy_user`.
+Since normally this is not required, the only way to enable prompting for both user/pw is to provide `proxy_authkey`
+that isn't actually in the authinfo file, then when not found, you will be prompted for user and pw. Alternately, if you provide
+`proxy_user`, but neither `proxy_authkey` nor `proxy_pw`, this will just prompt you for the `proxy_pw`.
+
+
 SSL/TLS:
 
 When Viya is configured to use TLS (HTTPS not HTTP), then the expectation is that the CA Certificate from the Viya
@@ -1019,6 +1030,14 @@ pw  -
     (**Strongly discouraged**) A password is required but if this field is left
     blank, the user is **prompted** for a password at runtime, unless it's found in the authinfo file.
 
+proxy_authkey -
+    (Optional) The keyword that starts a line in the authinfo file containing user and or password for authenticating to the provided `proxy` server.
+
+proxy_user -
+    (Optional) The user ID for authenticating to the provided `proxy` server.
+proxy_pw  -
+    (Optional) The password for authenticating to the provided `proxy` server.
+
 context -
     The Compute Service has different Contexts that you can connect to. Think Appserver in IOM.
     if you don't provide one here, saspy will query the Service upon connecting and get a list of available Contexts and

saspy/version.py

@@ -1 +1 @@
-__version__ = '5.1.2'
+__version__ = '5.2.0'