Clarity Post Action Identity
As of Clarity 2023 we have had the ability to set the task server to perform the post action locally. This applies to all post actions. The one thing to be aware of is, depending on the type of post action and where it is processed, the identity can be different.
Post Action |
Task Server Identity |
Web Identity (if different) |
BIM360 Upload |
360 Oauth Identity assigned to project |
|
BIMTrack Upload |
Default or BIMTrack Oauth Identity assigned to project |
|
Box Upload |
Default or Box Oauth Identity assigned to project |
|
Dropbox Upload |
Default or Dropbox Oauth Identity assigned to project |
|
Egnyte Upload |
Default or Egnyte Oauth Identity assigned to project |
|
Google Drive Upload |
Default or Google Oauth Identity assigned to project |
|
Microsoft OneDrive Upload |
Default or Microsoft Office 365 Oauth Identity assigned to project |
|
Microsoft SharePoint Online Upload |
Default or Microsoft Office 365 Oauth Identity assigned to project |
|
Microsoft Teams Upload |
Default or Microsoft Office 365 Oauth Identity assigned to project |
|
Move/Copy Files |
Task Server Windows Credentials |
Application Pool Identity |
Post to FTP |
Task Server Windows Credentials |
Application Pool Identity |
Procore Upload |
Default or Procore Oauth Identity assigned to project |
|
ProjectWise Check in |
Default or Projectwise Project assigned to project |
|
Run Script File |
Task Server Windows Credentials |
Application Pool Identity |
SharePoint Upload |
Default or Microsoft Office 365 Oauth Identity assigned to project |