How secure is the authentication of sync.blue® with external applications?

Which authentication methods are used?

sync.blue® prefers to use the OAuth2 method, provided the external application supports it. This means that no access data is stored locally on the system.

Why is OAuth2 more secure than classic password authentication?

With OAuth2, a temporary token is used for authorization, instead of a static password. This reduces the risk of sensitive access data being stolen, as there is no need to store passwords in plain text or locally.

How is communication secured?

All data is transmitted via HTTPS (transport encryption via TLS). This ensures that communication between sync.blue® and the external application is protected against eavesdropping and manipulation.

What are the advantages of the entire process?

• High security: Tokens instead of passwords and transport encryption reduce the risk of successful attacks.

• Easy administration: External applications can use their own authentication mechanisms, while sync.blue® only accepts and checks tokens.

Conclusion

Authentication of sync.blue® with external applications is very secure through the use of OAuth2 (if supported by the application) and the consistent use of HTTPS as transport encryption. Users benefit from a standardized and secure solution that does not store passwords locally and effectively reduces attack surfaces.