The problem we are facing is that... while registering the signature key it is asking for the registration key and private pin... i have created the private key in step 4 but i don't have any clue of what the registration key is or...how it looks like... .
I have - New JDE Keys Order and tried it but it failed.
so please help me in identifying the registration key .... it would be really great if u can show me samples of how a registration key will look like..
Registration key is a 10 digits registration pin that you have entered in the order form and private key password that you have created in step 4.
for full instruction read this article
Blackberry application signing
Related
I'm very simply trying to add a user to the device given the security name, auth key, auth protocol, priv key, and priv protocol using VB.net. At this point, NOT using VB.net is not an option.
SNMPSharpNet does not seem to have a solution for this problem. Open to all and any alternatives. If I would know what OID's to store these values in then I would be all set, so that would be extremely helpful as well. Also open to using the PowerSNMP library.
The answer is to set usmUserStatus + index of new user equal to 4 (CREATE_AND_WAIT) and then set usmUserCloneFrom to usmSecurityName + index of user you want to clone from.
I just deleted some of the fields of the Business Partner Window by logging in through System Administrator and now when I created fields again , and set their alignment , i need to enter the Search key Manually.
It doesn't fills automatically like before, If i just proceed with blank search key i get the following error:
-----------> MBPartner.saveNew: [POSave_31778910-6af9-4ff2-8736-0335ea702a4f]
Not inserted - C_BPartner[12]
-----------> GridTable.saveWarning: SaveErrorNotUnique - ORA-00001: unique constraint (E2DEVELOPMENT.C_BPARTNER_VALUE) violated
Any help would be appreciated!!!
I got the answer, the problem was due to deletion of all fields on tab and creating them again, the ad_sequence got corrupted. Once the ad_sequence was updated from backend Oracle the Business Partner started working fine again.
When a user is creating a new account and attempts to use a username that already exists, an error message is displayed by #Html.ValidationSummary(true) that says:
Name test#example.com is already taken.
I need to localize that string but cannot find it in the entire solution. Does anyone know where this string is defined?
The Identity 2,.0 is localizable via Nuget Packages:
Instal-Package Microsoft.AspNet.Identity.Core.XX
where XX is the desired culture (es, de, fr...)
There is no other way to do it.
Of course, you need to somewhat set the culture of your application: in web.config, programmatically, specified by the user's browser...
I am trying to run the Quickblox Video Chat sample to see if this is something that can be integrated to my app, but the sample setup is incomplete in how to get it to work.
https://github.com/QuickBlox/Sample-VideoChat-ios
I have created an app, put my app keys in the sample, and created 2 users and put their information there, but still does not work.
Please, when you put sample code write ALL the information you need to get it to work. The read me file mentions nothing about having to setup new users and even I figured this out, it still does not authenticate, just giving the error "Unauthorized"
This is the code they have for the users:
// This is test oppoents. This is 2 users' logins/passwords & ids
self.testOpponents = #[#"videoChatUser1", #65421,
#"videoChatUser2", #65422];
I created my own users in my registered Quickblox app and replaced the above code, but it still does not work. Is the password information supposed to go someplace here???? What is causing this to fail???
If you quickly go through whole sample, you can see some comments there
for example, look at this file
https://github.com/QuickBlox/Sample-VideoChat-ios/blob/master/VideoChat-sample-ios/AppDelegate.m
you can see comments that explain what all these values mean
//
// There are tests oppoents. There are 2 users' logins/passwords & ids
//
self.testOpponents = #[#"videoChatUser1", #65421,
#"videoChatUser2", #65422];
videoChatUser1 - login and password of the 1st user,
65421 - ID of the 1st user
videoChatUser2 - login and password of the 2nd user,
65421 - ID of the 2nd user
hope this help
I am trying to modify a D2L database from within a 3rd party application using their Valence API. I've gotten some operations to work but am stuck trying to create a new user account. I have been told that the account I am working under is authorized to do this.
I’ve defined a JSON object to hold the values I want:
{
"OrgDefinedId": "XX000TEST",
"FirstName": "Tom",
"MiddleName": "",
"LastName": "Foolery",
"ExternalEmail": "tom#something.com",
"UserName": "Tom.Foolery",
"RoleId": "78",
"IsActive": "true",
"SendCreationEmail": "false"
}
I copied the above text to the HTTP post buffer and then called the following link:
/d2l/api/lp/1.0/users/?
The parameter string contains the IDs and signatures (x_a, x_b, etc) as specified in the Valence docs. I assume the authorization values are correct, since I'm getting correct results when using the same algorithms on other Valence queries.
Any suggestions on how to get past the "Invalid Token" message would be appreciated.
--stein
If you're getting a 403 "Invalid Token" message then you are not, for some reason, forming your x_a, x_b, x_c, or x_d authentication tokens correctly. Common problems we have seen in the past are:
Trying to re-use x_c and or x_d signatures generated for one API call with another
Getting the tokens swapped around: x_a is App ID, x_c is App Sig, x_b is User ID, and x_d is User Sig
Generating the signatures using the wrong HTTP method (the method is one of the components of the base string for the signatures)
Not using all upper case letters for the HTTP method in the base string (the component should be GET not get)
Not using all lower case letters for the API route in the base string, or including incorrect characters: for example, in your question, you seem to imply that you're passing in the ? as a part of the route; you shouldn't do this. In this case, your base string for creating the URL should be POST&/d2l/api/lp/1.0/users/&1234567 where 1234567 should be replaced with the timestamp you generate and also pass in x_t
Using the API route with API version component provided, but when calling, using another version component (i.e. generating with /d2l/api/lp/1.0/... but calling with /d2l/api/lp/1.1/...)
Using an incorrect/mismatching timestamp value in the base string (the timestamp you use for the basestring should be in seconds, and be the same stamp as the x_t value)
While calls previously worked, suddenly none of the calls work with a 403 invalid token result: the user tokens could have expired and you need to re-authenticate the user
While calls previously worked against a test instance, when you try moving to a different LMS (prod instance for example) the calls don't work: perhaps the App ID/Key pair hasn't shown up on this new LMS, or you're trying to use the user ID/Key pair from one LMS to generate signatures on a different LMS
Also, notice that your JSON object is strictly not correctly formed: the IsActive and SendCreationEmail properties should have values of true and false respectively, not "true" and "false", although it's possible that the LMS parser on the server side will be forgiving about that.
If none of these points assist you, please feel free to open an issue in our issue tracker, or contact our Valence support email address, and we can try to help you out through this issue.
NOTE Please note that invalid tokens will throw you back a 403 (but the message will be "Invalid Token" or "Expired Token" or similar). If your tokens are correctly generated, but your calling user context is not allowed to create a user, then you'll also get a 403, but this time the message will be "Not Permitted" or "Not Authorized" or similar. Make sure you double check what sort of 403 you're getting back.
In this particular case, the permissions around creating a user are a bit tricky; not only must you have a permission to create a user, you must also have permission to modify the properties that you will be passing into the API in the CreateUserData structure (OrgDefinedId, Email, and so on), and you must also be able to see all those fields in the User Information Privacy settings, and you must have permission to enroll the user role you have provided at the organization level... those last two bits have tripped up some of our clients in the past.