I am just getting started with Azure Logic Apps and want to try connecting to SugarCRM.
I was pleased to see this guidance suggesting I should be able to find the SugarCRM connector in the Azure marketplace
https://github.com/Huachao/azure-content/blob/master/articles/app-service-logic/app-service-logic-connector-sugarcrm.md
However, when I try to find it by going to the marketplace on portal.azure.com and searching for SugarCRM, I do not see the connector in the results as described in the above link.
Either it is no longer published or I am doing something wrong. Do I need to do anything special to be able to access this?
I check this on the portal I could find it, then I consult the Azure official. The response is
SugarCRM was on product plan and later was removed. So it was never formally released.
So this feature is not available, if you insist on using this you could go to feedback and vote up this feature. When there are enough people vote for it, there is more chance for it to be added. Here is the feedback link:https://feedback.azure.com/forums/287593-logic-apps/suggestions/20565706-add-sugarcrm
Related
I need Azure AD users to be synced into my application, so I've been researching how to implement SCIM and configure Azure AD to work with it. My end goal is to have my application listed as the ones here: https://learn.microsoft.com/en-gb/azure/active-directory/saas-apps/tutorial-list, and to do this, it should support SSO + User provisioning.
The implementation is kind of straightforward as SCIM is a standard and I just need to implement a bunch of APIs complying with a specific contract, so this should work.
The problem I'm having, though, is I cannot find how to enable the "Provisioning" feature for my application. I've been reading the articles and watching the videos Microsoft provided (https://learn.microsoft.com/en-gb/azure/active-directory/app-provisioning/configure-automatic-user-provisioning-portal for instance) and it seems that when I click the Provisioning section in my app, I should be able to configure it. Unfortunately, I don't see the UI shown in the tutorials, so I suppose I've been missing some step that is not explained in the docs. Also, I'd expect to have somewhere to configure the base URL that should contain all endpoints required for the SCIM standard. I don't see this either, which confirms my feeling I'm missing something essential.
Here are the steps I've been taking:
Open the Azure portal
Create an enterprise app - Click on Enterprise applications, Create your own application, and Integrate any other application you don't find in the gallery (Non-gallery)
Once the application gets created, I can't see anything in the "Provisioning" settings
I found a solution to the problem I've described above. Unfortunately, I somehow the big blue "Get Started" button in the middle of the screen. When you click this button, the configuration I've been looking for appears and it is all good.
I've developed an application that works through Google's GSuite using OAuth2. The app is working fine and is part of the GSuite account that was set up to allow testing while developing it (which is the owning account of the app in the Developer Console). However, I now want to give the app to another GSuite company but can't see how to get them to add it?
The application has been submitted for review with Google to get it added via the Marketplace but we're keen to get the second company using it ASAP. I've had a look through the Google docs but couldn't find anything that appeared relevant and even tried to see if I could find an existing question on here. If anyone can point me in the right direction that would be much appreciated!
Cheers
You won't be able to give it to another company until it's published, so if the review is taking linger than expected, your best is to contact Google GSuite support
We're are about to build a new intranet system for our company, leaving SharePoint behind. The system will be built using Ruby on Rails. Since we're using Office365 for mail, calendar etc., we would like to authenticate our intranet users through Office365.
I'm aware of Microsoft Graph API, but I have a hard time figuring out of there is a possibility to authenticate users from a third-party application. Moreover, we would like to retrieve general information about the user, like profile picture and calendar information.
Is anybody knowledgeable about Microsoft Graph API and know if it's possible to achieve our goals using the API?
You're on the right track. You would authenticate with Azure AD, which is in the 365 ecosystem.
I wrote (and answered) a detailed guide here:
How to get the JWT (using OpenIdConnect) from HttpContext, and pass to Azure AD Graph API
Note that this is the OpenIdConnect flow. I think the Saml2 flow is somewhat different.
Don't take my advice on storing the authentication codes or try to acquire the token silently - it ended up causing issues in production that weren't seen in test. Rather, just use the user object id as your key attribute.
The microsoft documentation on the topic is a little cerebral and abstract, so it'll take a little head scratching, but have a look at the samples mentioned in the post I linked above, they'll get you started.
Yes, using Microsoft Graph is the right way to go about achieving the stated goals here.
There are quiet a few samples and tutorials provided on the Microsoft identity platform code samples page that will teach how to build an app that calls Microsoft Graph.
I'm struggling to get the best choice for me in terms of kind of license I need. I just want to connect my website using chatter through OAuth2 as well as I have been developing a canvas app. Everything has been done with my developer account in Salesforce but I have been wondering if I need to purchase any kind of salesforce license to use it. Even I have been wondering if I need a new license to upload my canvas app to salesforce appexchange.
I will be really grateful if someone could tell me something about it because I don't really know what I should do due to salesforce licenses are expensive.
Thank you so much
Diego
First thing I would suggest you to do is create a Partnerforce account here if you are planning to sell your app on appexchange. After that, log a case on partnerforce asking them how to go about it. They are helpful people and should be able answer your questions well.
To list the app on Salesforce you will have to follow certain steps:
1) Firstly join the DeveloperForce free.
2) Signup for Salesforce Partnership
3) Now through APO Create a Test Org and select Partner Developer Org
4) Through AppExchange you can easily publish your First app after packaging it.
5) You will also have to go through Security Review before publishing the app. After the security review you can easily be able to view your package on AppExchange.
To get live on AppExchange just these steps are to be followed or you can also take the help of any experienced or existing Salesforce partner to get complete information abput listing your app on AppExchange. They can guide and help you throughout the procedure and to pass the Security review as well of Salesforce. A well known Salesforce partner is Janbask, who provide Salesforce implementation service and can provide you assistance and consultation as well. As they are Salesforce partner so know how to complete the process.
Apart from this you can try any Salesforce learning or training institute, if you are in your learning stage who can provide you complete detail and solution of your problem. You can easily Integrate Salesforce and be able to view your app on AppExchange.
I'm using Google's user api on Google App Engine for authentification. As nearly everyone have a Google Account and api is easy to implement, that solution is convenient.
The problem is, though, with user who do not have a Google Account (or have no idea what a Google Account is). Where the api provides a nice interface to log in/log out and redirect immediately and easily to the app, nothing is said to developers about potential new users.
So here are a couple of things worth noticing:
Google' new Google Account page (https://www.google.com/accounts/NewAccount) is pretty straightforward, but not convenient at all for new users of a GAE app: no mention of anything not Google (users who don't really know what authentification is won't have any clue of why they need to open an account with Google), dead end (won't lead anywhere in the end), ugly.
GAE Log In screen includes a link to the New Google Account page. This link is of the form:
https://www.google.com/accounts/NewAccount?continue=http%3A%2F%2Fexample.com%2F_ah%2Flogin%3Fcontinue%3Dhttp%3A%2F%2Fexample.com%2Fprofile%2F&service=ah<mpl=gm&sig=0aa0a000aa000a00000aa0000a000aa
(Where example.com is the return url provided to the API). Great! But the situation is in no way different than it was: still a dead end, still no mention of any non-Google app, still ugly).
So, I'm asking, is there any imaginative way to provide a nicer interface for new users? Have anyone have ideas of how to present the process to the new users (a video for how to create a new account? some kind of tutorial page? etc.)? Just trying to think outside of the technical box here...
Regarding the various authentication options you can check out the Java or Python docs on OpenID (http://openid.net/)
Basically this allows supporting authentication by different agents, which includes Google accounts or even your own GAE application's custom implementation.
Furthermore you can check out User Experience summary for Federated Login for more information regarding UX considerations and best practices - with user authentication.