Can we reuse the context of an api that has been deleted? I am looking at the scenario, where someone accidentally deleted the api and want to recreate it. Or reuse the context for different purpose.
Currently, when I try do the same, I get an error - Error occurred while adding the API. A duplicate API already exists for "your api"
Is this a bug?
You should be able to use. But i think there is a reported bug regarding this.(not sure though) We will fix in the future release. But please, create a jira with all details.So, we wont miss it..
I delete and create new API's with the same name with both 1.6 and 1.7 and have no issue.
Related
(I have done a search through the questions to see if I could find something on this, but have not found answers.)
I have two google groups through my G-suite and I want to automatically add people to both groups after they sign up for my club through a process on my website. I think this should be possible using:
https://developers.google.com/admin-sdk/directory/v1/guides/manage-group-members
I have gone into the API Console, created a new project, enabled the Admin SDKI API, and got an API key. However, I think I am running into the Authorization issue because we keep getting an error that the authorization token is missing.
I have tried using the OAuth 2.0 but I'm not sure if this should be "Internal" or "External". I'm not creating a whole app for someone to use - all I want to do is on the back end of the site take information that comes through when someone joins the club and automatically have them added to my google groups.
Is it possible for someone to please explain to me what I need to do?
I'm sorry this is kind of a basic question.
Thank you for your help.
Trying to create SSO for AWS keeping Azure users as source of Truth. Followed below Tut's.
https://learn.microsoft.com/en-us/azure/active-directory/active-directory-saas-amazon-web-service-tutorial
http://blog.flux7.com/aws-best-practice-azure-ad-saml-authentication-configuration-for-aws-console
Anything is to be more precise with user attributes in Azure ? Has anything to enable in AWS to accept the SSO ?
Login is successful(Can see signin's in Azure AD) but it displays message "Your request included an invalid SAML response. To logout, click here
". Any idea what has gone wrong ?
Yes, I think you are on the right path. It seems that you are missing the custom attributes which we are suggesting to add for your application. Those are Role and RoleSessionName. Please see the step #5 in my article https://learn.microsoft.com/en-us/azure/active-directory/active-directory-saas-amazon-web-service-tutorial and make sure that you use the same casing and namespace for the claims. With that the integration should work correctly.
May be I am late to this post. As Jeevan mentioned. You are missing custom attributes that you need to add. I have been struggling with same and found this well explained video. I hope, this will help any one who is struggling with this issues.
We use WSO2 API Manager 1.10.0 for our API Management. I've previously setup an API which is restricted via scopes-to-role-mapping. Now we have to handle multiple versions of this API (not all clients can migrate to the new versions at once), but it seems I can't reuse the same scopes (scope-keys and scope names) I've restricted a previous version with?
This seems strange? Does that mean I need to create unique scopes-to-role-mappings for each version of the API? That would mean that subscribers using the /default api would have to update their scope-names when requesting an access-token depending on which version of the API they're using?
What strategy should be used here? We usually create scopes with scope-key <API-Name>-<Restriction-Key>. Should I now then use <API-Name>-<Version>-<Restriction-Key>, and when users migrate, they need to update their scopes when requesting an access-token to the correct version?
I really hope it's possible for our users to simply keep using the same scopes when switching to a new version of our API somehow, or are they uniquely tied to a specific version of an API?
Found an answer to this.
Firstly, if creating a new version of an API by using the "create a new version" in the publisher, the scopes can be reused; but as soon as you try importing a new swagger-specification the scopes are removed and can't be reused under the "manage-phase".
I found out that the scopes are actually specified in the swagger-document stored in the repository under /_system/governance/apimgt/applicationdata/provider/<provider-name>/<api-name>/<api-version>/swagger.json. The swagger-document has a property called "x-wso2-security" which includes the scopes (which is read by the publisher during the "manage-phase"). It's possible to add scopes to the swagger-document (for e.g. copying the x-wso2-security property from a previous API-version), save the resource and open up the publisher, the scopes will then show up to be used under the "manage-phase".
I assume this is something the WSO2-development-team has missed when creating the publisher, but happily, it's possible to get around it by doing some manual work as described above.
I've registered for the free developer account at smartfile [www.smartfile.com/]. It says I have an existing API key and API password, but nothing is not shown on screen.
It also prevents me from creating a new key and password pair. Is this a limitation of the "free account" ?
How do I view my applications/accounts default API key and password?
It's not visible anywhere.
The problem has been fixed now with a new update/fix.
Works fine with no issue at all.
Thanks for bring this to SmartFile's attention! Hopefully this will be helpful:
There was a two part fix to this issue. First, the database problem was fixed as soon as we found out about it. Second, we improved the dialog to show loading indicators and error messages if applicable. You can read more in our help forum thread here: http://smartfile.forumbee.com/t/q427a
Please let me know if you have any other issues!
I am having this weird error in sitecore user manager.
I get this error as soon as i open user manager
I can't assign users to roles.
Can anyone please help ?
Thanks in advance.
P.S > Just in case it's not visible properly : http://www.flickr.com/photos/24436387#N00/9030219859/lightbox/
Found this sdn post as well, refers to paging and databinding errors in the user manager should be fixed in your version of Sitecore though.
Although may give you something else to investigate.
Ok found the solution. I was using a third party provider (connector to salesforce) which was pushing campaign members to sitecore. And there was a bug in that API that was giving sitecore the wrong total null but only users.
Thanks for your help.