When I add a challenge question to existing challenge set ot create new challenge question set from IS 5.3.0 carbon console, and when I invoke the "getAllChallengeQuestions" operation in
UserIdentityManagementAdminService, it returns the only old set of challenge question. The newly added ones are not visible.
And also , when I add a new question using the "setChallengeQuestions" in admin service, its get added, and I could not see this newly added question in carbon console as well. And also If I invoke the "getAllChallengeQuestions" method after adding a challenge question, it only shows me the newly added one only.
There have been some changes in some of the feature implementations since 5.3.0. Therefore, you can not use UserIdentityManagementAdminService to manage challenge questions since 5.3.0.
You can use ChallengeQuestionManagementAdminService instead.
getChallengeQuestionsOfTenant
setChallengeQuestionsOfTenant
Related
I created a OAuth 2 client Id in Google Cloud Platform(GCP) in our production application. However this was only for internal use, so I removed it and tried to add it again in our development GCP project.
However when trying to add it, it says
Save failed
Requested entity already exists
Tracking number: xxx
What am I doing wrong? Do I need to do some extra steps to completely remove the OAuth 2 client id? I removed them around a month ago already, so it really should be gone by now.
It seems after 1 month the problem has automatically resolved itself. I assume it just soft deletes when you press delete, and then hard deletes one month later. Pretty annoying system.
You can also remove the entire project to get rid of unwanted ghost clients, but obviously you then lose all configuration.
The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.
I'm using Sitecore 8.2.170407
After reading this article, I tried to do several things:
Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work
Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
Image of patch class and Image of patch config
That didn't work either.
Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.
I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6
Have any of you been in the same situation before? How did you solve the issue?
If you need more information, please let me know.
Thanks in advance
You can't.
The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.
Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.
All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.
Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.
I'm using a free Microsoft Account (#outlook.com) on VSTS. I created my first proyect, configure it and make it works with CI/CD. Now, I'm creating a new proyect and I want to add a build definition, but I don't know why, all the options appears disabled.
No matter what I do, the Save button remains disabled.
¿There is a limited number of projects to use with CI/CD per account?
Thank's in advance
This is a very strange behavior, but finally I found the solution: in the querystring params you need to remove the "path" parameter (path=%5C)
Reference: https://developercommunity.visualstudio.com/content/problem/203956/build-definition-buttons-are-greyed-out.html
I created a API Connect project with command
apic loopback
When I try to launch the API designer, I receive error as below:
sdil#sdil-VirtualBox:~/Project/test-apic/todo4$ apic edit
The user model "User" is attached to an application that does not specify
whether other sessions should be invalidated when a password or
an email has changed. Session invalidation is important for security
reasons as it allows users to recover from various account breach
situations.
We recommend turning this feature on by setting
"logoutSessionsOnSensitiveChanges" to true in
server/config.json (unless you have implemented your own solution
for token invalidation).
We also recommend enabling "injectOptionsFromRemoteContext" in
User's settings (typically via common/models/*.json file).
This setting is required for the invalidation algorithm to keep
the current session valid.
Learn more in our documentation at
https://loopback.io/doc/en/lb2/AccessToken-invalidation.html
Error: loopback.errorHandler is no longer available. Please use the module "strong-error-handler" instead.
When I check for declaration in package.json, I did see strong-error-handler written.
"dependencies": {
...
"strong-error-handler": "^2.0.0",
}
How do i fix this to make API Designer running?
I sort of recognize this problem, actually. We had the new strong-error-handler but also the old one active.
Do the steps in "Migration from old LoopBack error handler" here:
https://loopback.io/doc/en/lb3/Using-strong-error-handler.html#migration-from-old-loopback-error-handler
Should eliminate the old one completely.
I'm not sure if this is the correct StackExchange site for this, so I apologize if it's not.
Is it possible to create subprojects in Redmine and have it automatically inherit the member permissions from the parent project? If I've got User A as Manager and User B as Developer on the parent, I'd like it to automagically set that up on the new subproject.
I've searched high and low and can't find a way - internal or plugin - to do this.
Thanks!
That's actually very simple: All you have to do is to go into the administration panel, display the list of projects, find the parent project and use the copy button to create the sub-project. On the next page you can configure your project, pre-filled with the values of your parent project, and have some more options like copying members.
Of course this works only on creation - once you created the sub-project and you change one project, you'll need to change the other one as well. Fortunately, working with groups makes it very easy (configure access for groups, not users).
This is possible now since Redmine 2.3.0 (see issue #5605 for discussion). When creating (or updating) a project, you can simply check the Inherit members checkbox.
(This option wasn't available in Redmine when this question was asked and answered initially, so I'd be happy if you considered changing the accepted answer to this one, thanks!)
That's not possible. One of the most fundamental facts of the Redmine permission system is that users are members of distinguished projects having one or more roles. The permissions can't be inherited. In fact, the possibility to have an issue tree was added rather late and hasn't yet been reflected in the permission system.
That said, even if it could be done, permissions could only be added, as you can't take away permissions using roles (permissions from multiple roles are always added). So you would end up with only the possibility to add more permissions in subprojects, but not with less.