We have clients asking to use SSO when logging in to BIM 360 through our app integration. Older posts indicate this isn't supported in Forge's OAuth. Is this supported yet?
Autodesk SSO is supported on Forge, however BIM360/Forge do not yet support others SSO such as google, apple, etc... - There is multiple sample showing the 3legged OAuth workflow using the Autodesk SSO. Here is one as an example.
Now if you want to use SSO from other organisations, note that this will be supported in future, so you may re-ask the question in future.
You could also decide to use a workaround that we did demo in this example, the workaround consists in asking the user to login twice the first time he visits your application (once on Autodesk SSO, and a second time on the other SSO) and bind the two systems in your database. Since you can refresh the 3legged token with a 14days period, you can keep your application connected to Forge/BIM360 as long you want. Note this is only valid for Forge; you cannot use that technique to log on the BIM360 application interface, only using Forge to work with BIM360 data.
Related
I'd like to have a page or a section of information that only is relevant to a specific API. Is that possible in the new portal?
In this case it has to do with information about event data that is sent out (to webhooks) when new items are created and that are then available in operations for the API. If it's not possible to have i an "API-specific" page, where would you put something like this?
I believe in this case you are trying to add some sort of static page or documentation to explain the functionality about a specific API. You may refer to this. As mentioned in the thread, you can try with swagger but in APIM portal it might not work immediately. Microsoft product team has confirmed that they working on improving support for OpenAPIv3. The ETA is about end of September.
However, you may also check the self-hosted gateway feature
The self-hosted gateway feature expands API Management support for hybrid and multi-cloud environments and enables organizations to efficiently and securely manage APIs hosted on-premises and across clouds from a single API Management service in Azure.
Official Documentation
I'm trying to obtain a full list of my project issues using the method described in the following document:
Issues - GET Issues
Quality issues
The list I get doesn't match the one available in the BIM360 portal. Quality issues are not common project issues.
Can you provide some examples or the set of methods available to get that information?
We found this thread is related to the Classic Field after having a live meeting today. To get issues from Classic Field, we need to use Classic Field API (link) instead, not the Forge BIM360 Issues API. Forge BIM360 Issues API can access issues data of the BIM360 Field Management and Document Management only currently. They are totally different systems. 😊
I am currently in the process of implementing pagination, sort and search functionalities in the project files/plans/sheets views of BIM 360 Docs integration.
Since I couldn't find any best practices regarding to these features, I thought I would reach out so that I don't keep stuck reinventing the wheel.
Background:
Most of the implementation uses https://github.com/Autodesk-Forge/forge-api-dotnet-client/ SDK.
Based on what I saw it looks like there is no built-in results sorting in the Forge/BIM 360 APIs. BIM 360 Docs looks as if it sorted results on the client.
One has to cache all the results as structured data on the client in order to provide the sorting functionality. That also does not play well with any pagination approach.
Question:
Is there a way to sort results using the API, so that they come back in a predefined order, also while paginating?
According to our engineering team, the "sort" feature isn't currently supported by Forge Data Management API. Apologizing for the inconvenience caused.
I have logged a request FDM-1813[Support sorting in APIs of BIM360 integration] in our internal system to our engineering team to allocate time to evaluate the possibility. As it required some time to complete this task, please remember this request id for the future reference. You're welcome to track updates or provide additional information by quoting this request id via forge.help#autodesk.com.
However, a workaround is to fetch all data from the API, then sorting on the client side via Javascript.
Cheers,
I'm confused by the preliminary documentation on the OneNote dev blog. Does it mean that a Native App accessing has to use (compile in) a Client ID specific to an individual O365 subscription?
The implication being that an Commercial App would need recompiling for each different O365 customer. Is this the intention?
If so then this severely limits the utility of OneNote Api in O365.
I'm hoping that I've misunderstood, can anyone advise please?
Paul,
Apologies if we confused you with our initial preliminary docs. Definitely not the case. The app ID is relative to the O365 tenant that publishes the app, but you just flip over the switch to say it is a multi-tenant app for it to be able to be consumed by any tenant.
I currently have a developer account setup in box and looking for steps to move it to production. I cannot find details on
If there is number of users allowed
How to turn production mode on
I am have setup initial account with auth redirect url. Configured my app key and token in my web application.
In terms of "productizing" I've heard a few different ways this term
1) To just make an app generally useable among consumers of the third party app, all that is needed is a functional integration with Box APIs. Assuming that you have implemented oAuth correctly and integrated our APIs functionally, there is no barrier to everyday users to using that integration between Box + third party app.
2) To make an app available to Box users ("productionalize" is a term I hear often), the best way to do this is through our gallery. Developers can follow these instructions for creating a listing in our App Gallery: cloud.box.com/appgallerylisting