| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #14 | 17271 | tjuricek | Remove deprecated Ruby implementation. | ||
| #13 | 17133 | tjuricek |
Altering SSL fingerprint regex's to work with 15.2 servers. Also, updating the version string dependencies in our Gemfile.lock to match the current client API version. |
||
| #12 | 17131 | tjuricek |
Always reconnecting after issuing "p4 trust" commands. We see sporadic failures in "p4 login -p -a" after this in testing, this may help. |
||
| #11 | 17117 | tjuricek |
Map 7857 to HTTP 403 error codes. P4WEBAPI-159 |
||
| #10 | 17108 | ptomiak |
Changes to enable automatic trusts. Implement a setting switch to automatically any new p4d we are talking to - mainly for GitSwarm. If a user will try to authenticate aganist a p4d we never saw before the fingerprint will be automatically accepted and login will carry on as usual. Added doc's section. |
||
| #9 | 16150 | tjuricek | If the system returns "login not necessary", return an empty string for the valid ticket value. | ||
| #8 | 16106 | tjuricek |
Revise the URLs for Helix Sync client workspaces. Added *stubs* for deleting the clients for a user, implementations will follow. |
||
| #7 | 16100 | tjuricek |
Add additional error code case of when to handle updating trust. Also, wrap p4 trust -y -f call in exception handler. For whatever reason, this occasionally will update the trust but return an error. When you do it again, the trust has already been correctly handled. |
||
| #6 | 16094 | tjuricek |
Move /auth/v1/login -> /projects/v1/login The more generic login method is now /helix_versioning_engine/vAPI/login |
||
| #5 | 16090 | tjuricek |
Rename ENABLE_AUTOMATIC_TRUST to ENABLE_MAN_IN_MIDDLE_ATTACKS and remove documentation. Only use this option for allowing developers to regenerate fingerprints on their own p4ds. |
||
| #4 | 16076 | tjuricek |
Use a TRUST_FINGERPRINTS file to decide which p4 trust fingerprints to accept. If we receive a request that is *not* in this file, and this setting is used, we reject it. This is our recommendation for production servers. The ENABLE_AUTOMATIC_TRUST is only to be used for testing servers. We need this because of a high-cost of the Qt test framework. Revised upon request of Alan Teague and Doug Scheirer. |
||
| #3 | 15894 | tjuricek |
Do not automatically update trust, just accept those that do not exist. ... if "autoaccept trust" is enabled. If servers change their trust certificates, well, they'll probably have to decide on either removing the trust file, or, manually editing it. |
||
| #2 | 15873 | tjuricek |
Added automatic calls to trust remote servers, if enabled in the system. It's enabled by default, but can be disabled for admins that do not want it. The p4trust file is moved somewhere writable by us. Also, disabling the p4enviro cache. |
||
| #1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
| //guest/perforce_software/helix-web-services/main/helix_web_services/lib/auth.rb | |||||
| #4 | 15073 | tjuricek | Update Auth::Middleware and add spec | ||
| #3 | 15059 | tjuricek | Tested authentication of the core /auth/v1/login method. | ||
| #2 | 15032 | tjuricek |
Starting config and doc revisions. System is now broken while revisions underway. Configuration of the p4d connection is now done via a single HWSSettings middleware object injected into the Rack env. The HWSP4Cleanup middleware now cleans up any p4 injected into the Rack env. The Auth::App class now mostly just contains one method to generate a p4 ticket. /auth/v1/login. Added yard documentation for the main project. Yard docs have been reconfigured to dump into build/ directories. This should probably be done with each release. Hm... The top level rake file contains a task, 'all:doc', to update our documentation. This should probably be run for each checkin. Hm... Specs are now using Rack::Test on top of a 'live' p4d. I'd suggest you still use the p4util mechanism, which now dumps to a /tmp folder, so we can safely add P4IGNORE rules back into your local .p4config file. Old 'perforce' application now called 'helix_versioning_engine'. Removing cache data. Helix Sync may be slow. It may also get axed. We'll see. |
||
| #1 | 13799 | tjuricek |
Start with branch specs hosting in a new monolithic 'helix web services' project. Converting from a microservice to a monolithic architecture due to resource constraints at getting a deployable system running. Additionally, since it's not expected that people will upgrade often, the major benefit of microservices - being able to add services individually without affecting others - is not really a major benefit. The Ruby SDK will be consolidated into a single 'helix web services client' project. It may end up being distributed via Rubygems. This only runs branch specs at the moment. I want to get a CD pipeline setup for the monolithic server before revising more methods. |
||