Password Requirements & StorageĪll passwords must be between 8 and 32 characters, with at least one uppercase letter, one lowercase letter, one number and one special character, such as are hashed prior to storage, using a one-way strong hash algorithm with salt. The certificate may be viewed by going to and clicking the padlock icon, located near the beginning of the URL in the address bar. The following protocols have been implemented for secure end-user authentication and access control: Certificate RequirementsĬonnections to Studio environments, such as, are encrypted using a Public Key Infrastructure-based (PKI) SSL certificate, issued by Amazon Web Services Certificate Authority (AWS CA). If your users aren’t receiving them, please ask your Email Server Administrators to check the Sender Policy Framework (SPF) record, and make sure that is also allowlisted as a trusted domain.
If you are only accessing a specific Studio environment, you only need to allowlist the domains specific for that environment, along with the required global services. Firewall Requirementsīelow are the domains that are used by Studio services environments. Primary communication and transmission of files, markups and other rich data uses the HTTPS protocol, while encryption and authentication uses the Transport Layer Security (TLS) protocol. Studio server connections are initiated by Revu clients, but the system does not send inbound connection requests back to the client. For more information, visit How to work in Revu 21 without a subscription. Also, Basics and Read-only accounts can’t create new Sessions or Projects. If you unlock the particular tool set and forget to lock it again, as long as file is not read-only, then the tool set will be released and saved when you exit Revu. Saving your current Profile will save the state of any modified tool sets.In Revu 21, non-subscribers without a Bluebeam Plan can still collaborate in Studio as Read-only users but will have limited access to markup tools and properties. If you have configured your environment to point to a shared network location, any tool sets which you make read-only permanently have the file unlocked for you and no other user can unlock the file. The file which stores the information for the tool set is saved as. Tool sets cannot be checked out by users who are offline. If nobody else has the tool set checked out, the lock icon will change to a Checked Out icon, indicating that the user can now modify the tool set (for example, to add, delete, or edit tools within the tool set).
Users with write permissions to the file can click the Lock icon to request to check out the tool set. A locked file is normally read-only so as to prevent multiple users from making conflicting changes to a tool set.Ī Lock icon in the Tool Chest panel indicates that a tool set is currently locked. Tool sets that are shared across the network are locked by default.
0 kommentar(er)
