21 docs tagged with "authentication"

To help third party developers write integrated applications, CollabNet provides an SDK.

Use the Configure Application tool to define your site level TeamForge settings.

To participate in a TeamForge site, a person must have a user account on that site. TeamForge administrators can create these user accounts. This topic applies to sites with no LDAP authentication.

To participate in a TeamForge site, a person must have a user account on that site. TeamForge administrators can provide access to multiple users by creating their accounts together.

When a user has trouble accessing the site, you may need to reset the user's password or change the user's account status.

To find a user, filter the list all Digital.ai TeamForge users on your site.

Memcached caches Subversion (SVN) authentication and authorization information and serves the mod_authnz_ctf module's authentication and authorization requests thereby reducing the number of SOAP calls, which in turn results in less load on the TeamForge Application Server.

Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.

If your site's users need access to an application or web site that is not part of TeamForge, you can make it available by linking or integrating from within your TeamForge site.

You can make it easy for project members to use a wide variety of applications and sites from within TeamForge.

You can query the database if you are a site administrator or have been given access to System Tools by another site administrator.

Here is some stuff you may need to know to work with integrated applications.

This is the sample application-policy block that you can copy into your login-config.xml file to support LDAP authentication.

These are additional details you can follow while configuring your email settings.

Follow these steps to convert your TeamForge installation to authenticate against your corporate OpenLDAP server.

An important aspect of the end-to-end development lifecycle is the creation and storage of software packages that are often binary artifacts. In the Java world, these are usually reusable jars that are used by other projects. Binary artifact repository managers are software systems that manage, version, and store binary artifacts. Example of such repository manager is Sonatype Nexus.

TeamForge provides a SOAP service for each tool in the application.

By setting up the SAML+LDAP IdP, TeamForge users can reap the benefits of both SAML and LDAP authentication mechanisms in a unified manner. With SAML+LDAP authentication, while SAML enables TeamForge users to access web applications, the LDAP authentication supports user authentication required for CLI applications. For example, if a user performs a source code commit in Git/SVN repository, the user can get authenticated via LDAP.

TeamForge supports integration with LDAP. Once integrated with LDAP servers, TeamForge can use LDAP credentials for user authentication.

With the new TeamForge Identity Management built on OpenID Connect (OIDC) and OAuth 2.0 authorization frameworks, TeamForge can now act as an ID Provider (IdP). As an IdP, TeamForge can authorize a third-party client application to obtain limited access to its services either on behalf of a Resource Owner (user) or on behalf of the client application itself.

SAML is an XML-based open standard developed by OASIS Security Services Technical Committee. It defines a framework to perform web browser SSO using secure tokens for exchanging security information between web applications.