What’s new

For help on multi-factor authentication:

• For the administrator, at the P4 command line, type p4 help mfa
  • This information is also available in the Administrator's Guide chapter on Triggers under "Triggering for multi-factor authentication (MFA)"
  • dm.user.allowselfupdate is a configurable related to MFA configuration
• For the end-user: p4 help login2
  • also available at p4 login2

This feature is currently supported for most Helix Core Server clients, including:

• Swarm 2018.1
• The 2018.2 releases of P4V, P4Eclipse, P4VS, and P4EXP

Commands to read or write against Git repos stored in the Helix Server within a Graph Depot are no longer in Tech Preview. See Graph depot commands.

• For a graph depot, p4 describe can use the "classic" syntax, or using the SHA1, can provide a commit description. See the p4 description Examples.
•  p4 filelog
• p4 fstat
• p4 print
• p4 revert
• p4 show-permissions (graph)
• p4 graph show-ref (graph)
• p4 graph tags

• p4 log - at the command-line, type p4 help-graph log

• p4 rebase - at the command-line, type p4 help-graph rebase
• triggers related to graph depots: see the What's New in the Helix Core Server Administrator Guide: Fundamentals.
• Support for Git Large File Storage (LFS).
  A replica can sync LFS files from graph depots.
  See the File Types chapter on File type modifiers, specifically the +F modifier.

• rpl.journalcopy.location be useful in a distributed environment. For details, see the Multi-Site Deployment guide on Configuring a read-only replica.
• To prevent p4 info from exposing sensitive fields, consider using dm.info.hide.
• p4 configure set now notifies you when you attempt to set a numeric configurable to a value outside of the acceptable range.
  Previously, a value below the minimum was silently altered to the minimum, and a value above the maximum was silently altered to the maximum. (Configurables already set outside the acceptable ranges will continue to be silently altered.)
• To prevent users from being created if they would have no permissions on the server, you can configure auth.ldap.userautocreate

• Additional security is available by using auth.tickets.nounlocked

• filesys.checklinks supports an additional value, 3

Stream path definitions can include a wildcard in the final expression of a path, following the last slash. You can use this feature to refer to a collection of files, such as path_type pattern/to/....exe or path_type pattern/to/*.txt
For examples, see theTo manage files of similar file-type in your stream specs, consider using wildcards (... and *) explicitly following the final slash in the path definition:

For details and examples, see the p4 help 2fa documentation and the Support Knowledgebase article, "Second Factor Authentication Support".

Please note that not all client applications have added support for second factor authentication yet.