Trello (Atlassian)
This guide explains how to set up single sign-on (SSO) between VaultysHub and Trello using SAML 2.0 via Atlassian Access.
Prerequisites
- Trello Enterprise subscription with Atlassian Access
- Administrator access to Atlassian Admin
- Verified domain in Atlassian
- Application configured in VaultysHub with SAML2
Note: SSO for Trello requires Atlassian Access, available only with Enterprise plans.
Configuration in VaultysHub
1. Create the application
- Log in to VaultysHub as an administrator
- Go to Applications → Add
- Create a new application:
- Name: Trello
- URL:
https://trello.com - Description: Project management and collaboration
- Icon: Choose the Trello icon
2. Configure SAML2
- In the Authentication tab
- Select SAML2
- Configure the following settings:
- Entity ID: the Entity ID of the Service Provider provided by Atlassian Access (and not the URL of VaultysHub)
- ACS URL:
https://auth.atlassian.com/login/callback - Format NameID:
emailAddress - App ID:
[appid](automatically generated unique identifier)
3. Retrieve the metadata
Note the following URLs:
- IdP Metadata:
https://[your-vaultyshub].link.vaultys.org/api/saml2/metadata/[appid] - SSO URL:
https://[your-vaultyshub].link.vaultys.org/api/saml2/sso/[appid] - X.509 Certificate: Download from VaultysHub
Single Logout from VaultysHub is not supported.
Configuration in Atlassian Access
1. Access Atlassian Admin
- Log in to admin.atlassian.com
- Select your organization
- Go to Security → Identity providers
2. Add a SAML identity provider
- Click on Add identity provider
- Select SAML single sign-on
- Configure the identity provider information:
Manual configuration
- Identity provider Entity ID:
https://[your-vaultyshub].link.vaultys.org/[appid] - SSO URL:
https://[your-vaultyshub].link.vaultys.org/api/saml2/sso/[appid] - Public x509 certificate: Paste the certificate from VaultysHub
Or via metadata URL
- Import from metadata URL:
https://[your-vaultyshub].link.vaultys.org/api/saml2/metadata/[appid]
3. SAML attribute configuration
Configure the attribute mapping:
<AttributeStatement>
<Attribute Name="email">
<AttributeValue>user.email</AttributeValue>
</Attribute>
<Attribute Name="firstName">
<AttributeValue>user.firstName</AttributeValue>
</Attribute>
<Attribute Name="lastName">
<AttributeValue>user.lastName</AttributeValue>
</Attribute>
</AttributeStatement>
4. Domain configuration
- In Domains, add your business domain
- Verify the domain via DNS (TXT record)
- Enable Enforce SSO for this domain
5. User assignment
- In Users, configure:
- Auto-provisioning: Enabled
- Just-in-time provisioning: Enabled
- Update user details on login: Enabled
Group and permission configuration
Group synchronization
VaultysHub does not transmit groups in the SAML assertion. Groups and permissions are managed directly in Atlassian Access.
Trello permission mapping
In Atlassian Access:
- Directory → Groups
- Create your groups and add users to them
- Assign each group the desired role (Workspace Admin, Normal User, Guest User)
Workspace configuration
To automatically assign users to the correct workspaces:
- Products → Trello
- Workspace access
- Configure access by group
Security policy configuration
Session and authentication
- In Atlassian Access → Policies
- Configure:
- Session duration: 8 hours
- Require re-authentication: After 30 days
- Mobile session: 90 days
IP restrictions (optional)
{
"ip_allowlist": [
"203.0.113.0/24",
"198.51.100.0/24"
],
"enforce_for_admins": true
}
Configuration testing
1. Connection test
- Open a private browsing window
- Go to trello.com/login
- Enter your business email
- You should be redirected to VaultysHub
- Authenticate with your VaultysHub credentials
- You should be logged into Trello
2. Test with the mobile app
- Open the Trello mobile app
- Tap on Log in
- Enter your business email
- The app opens a browser for authentication
- After logging in, you are redirected to the app
3. Permission verification
# Via the Trello API
curl -X GET "https://api.trello.com/1/members/me" \
-H "Authorization: OAuth oauth_consumer_key=\"{key}\", oauth_token=\"{token}\""
Integration with Power-Ups
Power-Up configuration with SSO
For custom Power-Ups using authentication:
// Power-Up configuration with SSO
const t = window.TrelloPowerUp.iframe();
t.authorize({
url: 'https://[your-vaultyshub].link.vaultys.org/api/oidc/[appid]/auth',
clientId: 'trello-powerup-xxxxxx',
scope: 'read,write',
expiration: '30days',
name: 'My Power-Up'
});
Automation with Butler
Butler configuration with SSO
Butler automations continue to work with SSO. For custom commands:
when a card is moved to list "Done" by anyone,
post comment "@{username} has completed this task"
Troubleshooting
Error "SAML response validation failed"
Problem: The SAML response is not valid
Solution:
- Check the X.509 certificate
- Ensure the Entity ID matches in VaultysHub:
https://[your-vaultyshub].link.vaultys.org/[appid] - Check the logs in Atlassian Admin:
- Security → Authentication log
Error "User not found in directory"
Problem: The user is not provisioned
Solution:
- Check that the email domain is verified
- Enable Just-in-time provisioning
- Check the email attribute in the SAML assertion
Groups are not synchronized
Problem: Group permissions are not applying
Solution:
- VaultysHub does not transmit groups: group membership is managed in Atlassian Access
- In Atlassian Access, check Directory → Groups
Mobile error "Authentication failed"
Problem: Authentication fails on the mobile app
Solution:
- Ensure the SSL certificate is valid
- Check that the callback URL is allowed
- Try completely logging out and logging back in
Security
Recommendations
- Enforce SSO: Enable SSO application for all users
- Domain verification: Verify all your business domains
- Session management: Configure appropriate session durations
- Audit logs: Regularly monitor authentication logs
- API tokens: Manage API tokens separately from SSO
Compliance configuration
{
"compliance_settings": {
"data_residency": "EU",
"encryption_at_rest": true,
"audit_log_retention": "365 days",
"gdpr_compliant": true
}
}
Backup and recovery
In case of issues with SSO:
- Administrators can use the recovery email
- Atlassian Access maintains emergency access
- API tokens remain valid regardless of SSO
Integration with other Atlassian products
Jira and Confluence
The same SSO configuration automatically applies to:
- Jira Software/Service Management
- Confluence
- Bitbucket
- Opsgenie
Unified configuration
atlassian_products:
- trello:
enabled: true
default_workspace: "enterprise"
- jira:
enabled: true
default_project: "PROJ"
- confluence:
enabled: true
default_space: "DOCS"
Migration of existing users
Migration script
# Script to migrate users to SSO
import requests
def migrate_users_to_sso(domain):
# Retrieve all users
users = get_all_users(domain)
for user in users:
if user['email'].endswith(f'@{domain}'):
# Enable SSO for the user
enable_sso_for_user(user['id'])
# Send notification email
send_migration_email(user['email'])