Azure B2C Provider in DNN - azure

i am using B2C provider for DNN and trying to install it as extension and it's throwing error https://i.stack.imgur.com/6faW1.png
i am trying to use multiple version as well but not installed properly and using source from https://github.com/intelequia/dnn.azureadb2cprovider/releases
Please help me out.

There was an issue in the DNN manifest file that has been solved on v1.4.7 (release https://github.com/intelequia/dnn.azureadb2cprovider/releases/tag/v1.4.7). Tracking the issue at https://github.com/intelequia/dnn.azureadb2cprovider/issues/19

I wrote the answer below before seeing this: https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
Perhaps this is pertinent to your question. You might want to check with Ryan Moore (moorecreative" to see if he was able to resolve the issue.
First, please bear in mind that I am not familiar with this particular extension, but it seems as if it is "just another" authentication provide for DNN.
I'm also a little confused. The error message indicates that you've already installed th Intelequia AzureB2C provider. Is that true?
You also say "I am using" and then "trying to install it as an extension." If you are using it, that means that it is already installed as an extension, so a second attempt to install it should throw an error. But, I would think that the installer should see that problem earlier in the process.
Finally, you say "i am trying to use multiple version as well." A provider should be installed only once, and that is what the error message is telling you.
Once you have installed an authentication provider you typically enable it for a portal, and it becomes part of the authentication process.
You should read the documentation carefully, and make sure that you are trying to use the provider as the developer intended.

Related

Youtube API Node.js quickstart not working: "The API returned an error: Error: invalid_grant"

I followed the tutorial Node.js Quickstart, including installing the libraries googleapis and google-auth-library. I believe I followed the instructions for setting up the credentials properly to my best ability, but I lack the experience to know for sure.
I was unable to exactly follow the tutorial, specifically this line:
e. Select the application type Other, enter the name "YouTube Data API Quickstart", and click the Create button.
because the drop down selection box had no "Other" type.
I had a project using this system working in the past, but it suddenly stopped working. I had not used the program for months, so it is possible something happened in the meantime, but I also absentmindedly revoked the program's access to my Google account.
I am not using the same credentials as before it broke -- in the developer console, I not only deleted the old credentials and downloaded brand-new ones, I created a new project altogether.
Here is an image of the credential:
Of course, I downloaded and renamed the client_secret JSON as instructed.
Here are my project files:
Since I directly copied the code, I have not tried changing it, though I did look through it to make sure there were no IDs I needed to copy in or anything of the sort.
I tried looking through this article, but I had no idea where to even begin the stated debugging processes, as my only experience with OAuth, Node.js, and the YouTube API is this project, and I don't even understand how I got it working originally.
If anyone has any ideas on ways I could try fixing this, or more thorough instructions on how I could begin debugging, I would be immensely grateful.
If relevant at all, I am using the WebStorm IDE.
Screenshot of the terminal:

Azure Communication Services with Ionic

I have a working project with Twilio + Ionic, but I'm wondering if you can help me with adding Azure Communication Services(video call) into my project. I tried to follow the example from the official website, but I think it's not just installing npm library and adding it as usual in my project.
If you want to see a working sample, you can use this: https://github.com/Azure-Samples/communication-services-web-calling-hero
If you're still stuck, please respond here and I'll try to help you directly.
Invalid CommunicationUser identifier specified

If I provided incorrect subdomain name during Kabanero Foundation installation, how to fix it?

I provided incorrect subdomain name during Kabanero Foundation installation on OKD. Now my Application-->Routes are wrong. How to fix that?
For Kabanero Landing Page, my link is: https://kabanero-landing-kabanero./
I tried https://kabanero-landing-kabanero./ but I get
Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Expected: Kabanero Landing Page
Actual: Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
There really is no good way to fix it. There is not a good manner to change the routes automatically. Assuming you are early in your install, you should be able to clone the 0.2.0 (if you installed 0.2.0) support scripts from https://github.com/kabanero-io/kabanero-foundation/tree/0.2.0/scripts and run the uninstall-kabanero-foundation.sh script to remove the foundation and reinstall. You should be able to keep the OKD install that you have done.
If there are enough people that hit this, I can put a requirement in place to provide an update script to change this value and restart.

Plugin registration tool throwing Unable to load plug-in assembly

I'm using the latest version of the MS CRM 2011 SDK and am trying to deploy a custom workflow activity (it has been signed with a key). The plugin registration tool throws an error "Unable to load plug-in assembly" without much information about the root cause.
The error trace thrown by the tool is very similar to the one described in this post
The answer to the post referenced above indicates adding Microsoft.Xrm.Client assembly in the GAC, but my workflow project references the following DLLs
1)Microsoft.Crm.Sdk.Proxy.dll
2)Microsoft.Xrm.Sdk.dll
3)Microsoft.Xrm.Client.dll
4)Microsoft.Xrm.Sdk.Workflow.dll
Should all these be added to the GAC?
The CRM server is Win 2K8R2. I tried dragging and dropping the assemblies to the c:\windows\assembly folder but that did not work. No errors but nothing was copied over either. I followed the instructions outlined in this post but that did not work either.
What am I missing?
I don't think you should have to place any crm dlls into the gac, they are already installed in the CRM server files. If you think it might solve the problem use gacutil (not clear if you can't install to the gac, or if that didn't fix the problem).
I suspect its complaining about your dll, are you trying to register to the disk? As you usually have to place the dll in the crm/server/bin folder first. Try deploying to the database - makes life easier for deploying the solution to other servers later.
If that still doesn't work post the trace of the error.
Turn on crm server side.tracing. You'll get much better error information. Use the CRM diagnostic tool to turn on trace logging: http://crmdiagtool2011.codeplex.com
Turns out that if you use the /codecustomization switch to have the code generator derive from "CrmOrganizationcContext", you need "microsoft.xrm.client.dll". This DLL is not included in the default install of CRM and you need to get this on the server one wa or another.
I decided against using the /codecustomization switch which causes the "context" to derive from "OrganizationContext" instead and not take a dependency on that DLL. Plugin registration now works! This post provides more insight

Spotify apps dead after update?

I was developing a Spotify apps and all of the sudden Spotify restarted and updated.
Yey, great.. I got version 0.8.3.222.g317ab79d... however typing spotify:app:the_app_name doesnt work anymore. I get metadataFailed, sorry I could not find this app.
Anyone knows where I can find a downgrade?
Spotify 0.8.3 changed the app lookup slightly. The URI for getting at apps in development is now spotify:app:application-identifier-in-manifest.
This changes the behaviour in old versions, which used the application's directory name to load applications. It's also worth noting that your application must have a valid identifier and version in its manifest.json file. Remember to restart the client when changing your manifest so it notices the changes!
The keys you need to set are BundleIdentifier (which will be used to find the app) and BundleVersion. Documentation on the keys can be found here.
When you check spotify.com you can see there is a be right back message this indicated either server or application failures just hold for a few minutes/hours and return to developing after message is gone.

Resources