Since the developer site update the other day, I have lost access to the sandbox.
I was literally using it an hour before the update.
I tried to retrieve my password, but my account is no longer found.
I tried to set up a new account, and it's telling me that I need to have a US registered business in order to sign up.
So, my question is, what does the rest of the world do when they need to test their site?
Am I missing something?
Thanks
Simon
Ok, Got it. PayPay support have said to create a dummy account. In other words, lie about having an American business. Once you've done that, go to applications, then sandbox accounts, and import the data using your old sandbox credentials!
I have the same problem. It appears to be even worse than stated. They appear to have 'integrated' the Sandbox login with PayPal account logins. So you have to have a live PayPal account. In other words developers must also be CFOs in their organizations, or else must be using PayPal as a means of exchange themselves, otherwise they don't exist.
Truly incredible.
Not to mention having cut off arbitrary numbers of existing developers in mid-stream.
Related
A client granted me access to their Google Analytics. I need to share it with my contractor however I don't want them to access my Gmail. How can I provide them my login for Analytics and restrict them from accessing my Gmail.
(I'm trying to not bother the client and I don't have the right privileges to add another user to their Google Analytics account)
Thanks ahead of time!
If you give access to your Google Account to the contractor, of course it will also see Gmail.
Solutions:
Ask for access for the contractor;
Create a dashboard that reads data with Google Analytics API and share that with the contractor.
It's a Pickle 🥒
Straight from the get-go, I feel you. I've been in similar situations multiple times. It's a pickle of a situation. However, I think there is a good solution for you:
Ask your client for administrator access.
Now hold up! This may seem like something that will bother them, but it's something that will allow you to do the work you need to do. They want you to do a good job and have the tools to do it, and having admin access will allow for that. You wisely, do not want to share your login credentials with your contractor.
Reasoning 🤔
Having said that, it is my natural inclination to not ask a client to do work. It feels like an inconvenience to them, that they're paying me to do the work, and that they aren't paying me for them to do work. However, I've been training myself to think differently about that. I've been trying to reframe the relationship between us and clients like it's a partnership, that we're on the same team, and that we're both going to have to do work to see the project through to completion. I need to be able to ask the client to do work, like set up accounts, provide content, review edits etc. It's furthermore an exercise in trust. If they don't trust you enough to grant you admin access, it's your job to help them see that they need to trust you in order for you to do great work for them.
And they want you to do great work.
Strategy 🚀
I generally have my clients give me administrator access to all accounts that I need to manage. That way I can make any changes needed to the account and add users etc. I would have ran into a similar problem earlier today (the client granted me access to their Analytics account with my individual business email, instead of our joint email account that we use for those kind of activities). However, since I had asked them to give me administrator access, I was able to add our joint account as a user and remove my individual account.
Specifically in your situation, I would not recommend sharing your login information with a contractor. I think that is the only way of getting around getting admin access to their Analytics account.
I hope that helps you navigate that situation! Try to reframe the problem as an opportunity for some practice to ask your client to do something. It may seem be hard, but it will help so much in this situation, and for other situations where having the client do a bit of work will make your work and the project so much better.
You've totally got it! 😁
I'm looking for a Voice Authentication API, and I find Microsoft's one.
When looking at prices, it asks you for a region. The problem is that
it only shows a region
I've been reading about Azure's regions, and it say that is where data is stored, so my question is if it would be possible to use it in a different region than allowed.
Thanks (and sorry for my spelling mistakes).
Quick Answer:
Normally yes, but currently the Speaker Recognition API is only offered out of the WestUS datacenter.
If it's mandatory that you have low-latency when using the service, I suggest you look into setting up and/or temporarily subscribing to a CDN service. Or, if you have a lot of time on your hands, and know waaaaay more than I do about this subject, you may be able to design a local cache to mitigate latency if you're distant from WestUS.
Less-Quick Answer:
First off, you should use the dashboard interface at https://portal.azure.com to sign up. You will first need to create a Pay-As-You-Go subscription as your payment-medium, but it will give you much more control over & visibility into your service.
Here's what the signup pane looks like inside of https://portal.azure.com:
It appears that, in it's current "PREVIEW" deployment, you are right the services is only offered from the the WestUS data center. Normally you will have the option to one of ten's of global datacenters, but it is common that PREVIEW services aren't deployed globally until they're out of PREVIEW status.
If the problem you are looking to remediate is latency-based, look into the CDN suggestion in my "Quick Answer."
If your issue is about getting different pricing based on your location, the location of the datacenter you choose will not affect this. If geographic-discounting applies to you, it is based on the country that is assigned to your Microsoft Username/Password combination at the time it was created. This value cannot be changed once a username/password combo has been created, and consequently, any payment info used along with this uname/pass will need to have a billing address in the same country.
I'm totally new to SAML. I want implement SSO for my ASP.NET Website. I got the SAML assertion from my client. I would like to know what are all other requirements I need to get it from my client and what setup I need to implement at my end.
Can anybody help me out in this.
Thanks in advance.
The first thing that I would do is avoid writing the SAML code yourself. There's plenty out there. #Woloski (above) has some. My company has some (I work for the company that makes PingFederate). There's some open source stuff, too. I've seen good connections from KentorIT authServices. If this is your first foray into SAML, then my bet is that ADFS is way overboard. I'll be honest, the groups we see most commonly at Ping is when they decide to go "all in" with SSO. The first one or two connections are easy. Tehn it becomes a management nightmare rapidly thereafter. The reason I say to avoid writing your own, is because there are a LOT of nuances to SAML, with massive pitfalls, and headaches you just don't need.
As the service provider (SP), you need to tell your client (Identity Provider, or IdP) what "attributes" you need from them to properly connect their users to their account in your application (maybe a username?). In addition, you can ask for additional attributes to ensure their profile is up to date - phone number, email, etc. It's up to the two of you to determine what you need (and what they'll give you). Obviously, they shouldn't send social security number, if you have no need for it.
You also need to decide if you will do SP initiated SSO (will the users get links to documents deep inside your app?), or if just IdP initiated (Or will always just come to the front door?) will suffice. What about Single Logout? Do you (or they) want to do that? [Personally, I suggest NO, but that's a different topic]
What about signing the assertion? Your cert or theirs? If you're doing SP-init, do you need to use their cert or yours for signing the AuthnRequest? Do you need encryption of the assertion, or maybe just a few of the attributes?
Generally, you do all of this with a "metadata exchange". You give them your metadata that says "this is what we need". They import that metadata to build a new connection, fulfilling the attributes your app needs with calls to their LDAP or other user repository, as well as doing authentication (if required). They finish building their connection, and export THEIR metadata, which you import to build your connection (thereby making sure you all agree on certificates). You hook it to your app, and away you go.
I make this sound easy. It is, and it isn't. Rolling your own can mean issues. Lots of them. With some being so minute that it takes pros hours (and days) to see it. When it works, it works, and well.
HTH -- Andy
you can use something like ADFS to accepto SAML Assertions. ADFS gets installed on Windows 2008 or 2012.
You would need to ask your customer
the signing certificate public key and
the sign in URL.
Then you would create a "Claims Provider Trust" in ADFS and enter those details. Then a "Relying Party Trust" that represents your application. Finally you would have to configure your application with ADFS using WIF. This blog post have more details:
http://thedotnethub.blogspot.com.ar/2012/12/adfs-20-by-example-part1-adfs-as-ip-sts.html
Also you can use Auth0 to accomplish the same without setting up any software on your side (disclaimer: I work there).
This question is not related to ASP.NET specifically, but more web applications in general.
I am building a web application wherein I am registering a user. As of now I am taking in very basic credentials like First Name, Last Name, etc of the user. In this website I am giving some information for free for any user who has just registered so that the user finds my website authentic and that it is not a fake website. After that, to get more information, the user has to pay.
The information my site provides will get obsolete after sometime. So, when a new user registers, he/she will get the new information that gets updated; but the old users have to pay to get the same new information.
My problem here is once the information gets obsolete the same person can re-register with a different set of credentials and get the new information. I want to avoid this from happening.
So my question here is this: what information should I request from the user, or extract from the user, to check that the same user is not re-registering? Or any other way to make this possible.
I am thinking of getting the IP address of the machine from which the person is registering and use it to check. But the user can use a different machine to re-register.
I am completely lost here and not getting the solution. I even checked on the Internet but could not find an answer.
Please let me know if you need any further information from my side.
You will not find a technical way to prevent users from registering multiple times. They can simply use another device, IP, another email account and different credentials.
What you can do is asking them to send you hard to fake "offline" information, like a credit card number or a photo of the ID. Some users may still be able to register multiple times this way, but probably not indefinitly. You will however lose many possible clients this way who are unwilling to provide such information for a test account, so this is likely not the solution you want.
My advice would be one of the following two:
Limit the information/service you give out to free users, so that even if they register again they will gain something when they pay.
Try to bind them to their account in a way where they would lose something if they threw it away. This may for example be providing user rewards for activity (real or virtual) or increasing their experience based on their history. Take SO for example: If you registered again, you would lose all your reputation. The users will think twice if this is worth the new content.
After reading all of the above, i think a good solution could be to let the user identify himself through facebook or linkedin. Few people will have a second account.
I think you cannot put any users like that because every thing can be duplicate
There are some ways for which the user must have payment mode or identity details like passport or it is windows application you can have finger scanner it will be definitely Unique..
You can do this (with limitations) with the use of cookies. Setting a cookie on the users device will allow you to determine who the visitor is and that they have already registered.
The limitations are that cookies can be deleted or blocked and are only valid for that specific user agent - the user could use a different device or a different browser on the same device. A lot of people don't really know about cookies though and how to delete them.
By tying this technique with a requirement to provide a valid email address you can make it a hassle for somebody to register more than once as they will have to create a new email account and then delete their cookies.
Whether this will stop enough people depends on your site and your requirements - if you're giving money away then this technique is not nearly good enough. If you just want to discourage the practice of multiple accounts it may be enough.
Your only way out is to have SOMETHING the existing user gets as a "gift?" or added value to maintain just one account. If you can identify items of value to your subscribers and offer to "give" it to them provided their account "attains" one or more status, then you'll get some control. Take stackoverflow.com for example, I don't need a second account.
Identifying by facebook or linkedin is a good option, but if you are giving such services. which are very beneficial for the users, so they dont mind on creating multiple accounts on even facebook or linked in.
So what i think is to set some reward type stuff with each user, and increase the services as they get increment in rewards.once they are good in rewards and are capable to use multiple services, this increases the probability that they will not create another account.
So i found several questions on SO about ASP.NET and hosting, but none of them (as far as i could find) quite answered my question.
Basically, I'd like to be able to temporarily deploy websites I work on to a server so that I can verify that the deployment process goes okay. Essentially, I'm looking for a "trial" hosting that doesn't require a follow up purchase; temporary hosting.
Does anyone know of any such thing? OR, would I be better off just getting myself a separate computer that I "host" from home and deploy to that?
Have a look at https://www.gearhost.com
I use them for my projects and they have free plan which is not limited in time, just resources.
https://youtu.be/rgAWMl-gccM
You can use reliable they come with a 15 day money back guarantee. So if you think you can do what you need to do in 15 days then you can do this.
However you probably will see need to pay first and then request your money back. I would think most will do that I never seen a hosting site yet where they give you X days without any sort of registration and at least put a credit card down.
15 Day Money Back Policy(Reliable Policy)
If for any reason within the first 15
days of your period with us you wish
you cancel your account, then we will
issue a full refund with no questions
asked. To request a refund please
submit an account cancellation ticket
using our billing portal at
http://payments.reliablesite.net. In
the reason for cancellation please be
sure to list a request for your
refund. If no request is listed no
refund will be issued. Please note
that domain names, domain transfers,
and SSL certificates, dedicated
servers, and virtual private servers
are non-refundable.
Won't you need hosting after? I am unclear why you want to check it on a server to make it sure it works but then take it down and not host it anymore.