Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.5f1
Issue ID
1176467
Regression
No
[VCS] Support for Perforce two-factor auth (MFA, using "login2" command)
Newer perforce instances sometimes enforce 2-factor authentications.
Result: Unity's perforce integration will try to force a login on each launch instead of caching credientials.
Expected: Cache credentials
Code looks like it is using the old p4 login api call that does not seem to deal with MFA (https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_login.html)
New API login2 (https://www.perforce.com/manuals/v18.1/cmdref/Content/CmdRef/p4_login2.html) with argument -p should be able to handle credential caching.
Seemingly the MFA thing was added in Perforce 2017.2, we should probably keep using the old login command for older versions.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- WebGL builds report wrong screen resolution if "matchWebGLToCanvasSize" is set to "false"
- List<T> in the Inspector does not update values when changed through Dropdown menu
- Crash on keywords::LocalSpace::Find when reimporting specific assets
- “Command Line Arguments” window in Hub becomes distorted with long project names
- "Save" button is displayed as active in the Hub "Set project display name" window
Resolution Note:
Due to the complexity and the risks of the fix we've decided to not change the current behaviour with Perforce's multi factoring login. In order to login correctly in the Unity Editor you will need to first login using a visual client like P4V or via the command line using login2