Installation Requirements
Client requirements
Minimum requirement for installing Alfred Desktop client:
- Hardware: Any modern business desktop/laptop meeting the
requirements of the installed operating system capable of running
your preferred productivity suite (e.g. Microsoft Office).
- Operating System: Microsoft Windows 10 or higher
- Runtime: .NET 9 Desktop Runtime
- Available disk space: 90 MB for initial installation and first
server connection
Backend Requirements
The Alfred API and Alfred Desktop Backend modules are installed on your
existing Alfresco Instance/Server. Minimum requirements for running
Alfred modules:
- Hardware: Any recommended server configuration/hardware for your
Alfresco version and business needs.
- Operating System: Any operating system supported by your
Alfresco version.
- Runtime: Alfresco 7.0 Community/Enterprise edition or higher
Alfred Desktop 5.0 requires at least the following versions of the
backend components:
- Alfred API module: v6.1.0
- Alfred Desktop backend module: v4.4.0
Feature Requirements
- Edit Online:
- Microsoft Office 2016 (32 or 64-bit) or higher
- Alfresco Office Service module on the Alfresco Server
- Convert to PDF:
- Microsoft Office 2016 (32 or 64-bit) or higher
- Compare documents:
- Microsoft Word 2016 (32 or 64-bit) or higher
- Metadata auto-completion:
- Requires SOLR-based search on the Alfresco server
- Facetted search:
- Requires SOLR-based search on the Alfresco server
- OpenID Connect authentication:
- Alfresco configured for OpenID Connect
- A public client at the identity provider (see below)
OpenID Connect Authentication
As of Alfred Desktop 5.0, the client handles OpenID Connect
authentication itself. Alfred Edge is no longer required, and
authentication through Alfred Edge is no longer supported.
Alfred Desktop re-uses the OpenID Connect configuration that is already
in place for Alfresco. It reads the client id and the scopes from the
redirect that Alfresco returns, so there is nothing to configure in
Alfred Desktop itself: the user only selects “OAuth - OpenID Connect” as
the authentication method of the bookmark.
Two things have to be true at the identity provider:
- The identity provider has to allow
<repository URL>/alfd/oidc/intercept as a valid redirect URI, on
the client registration that Alfresco uses. In most set-ups this is
already the case, because the redirect falls under the normal
repository URI and the valid redirect URIs are registered as a
pattern under that same base URL.
- The client registration that Alfresco uses has to be a public
client. Alfred Desktop authenticates with PKCE (S256) and does not
send a client secret, so a confidential client that requires client
authentication on the token endpoint will refuse the request.