Hi, 

is it possible to change my email address?  I currently signin with Apple and I no longer want to do that.

Neither do I want to use Google.

If I create an account at https://myaccounts.wizards.com/ with the email I want to use, will I be able to use that account to login to D&D Beyond?

Thanks

You cannot use your wizards account to log into D&D, that's just an optional feature for linking.

You are still required to use a Google or Apple account to authenticate your account.

You can unlink one of those accounts, but not both and it's recommend that users have at least two authentication methods linked to their account.

Quote from Davyd >>

You cannot use your wizards account to log into D&D, that's just an optional feature for linking.

You are still required to use a Google or Apple account to authenticate your account.

You can unlink one of those accounts, but not both and it's recommend that users have at least two authentication methods linked to their account.

 
Oh, that makes me somewhat sad, because I wanted to unlink my Apple identity from as many online locations as possible.  

Do you happen to know why we are forced to use Apple or Google? 

It seems a strange decision.  

Also, although I have a Google account linked, I have not used that account in years.  It no longer exists as Google has deleted it in accordance with my moratorium settings, so I can not remember the password and there is no way to reset the password.

Do you happen to know how I can get that account unlinked?  Surly it can be done behind the scenes.   

I believe I explained this to you before in a different thread.

Google and Apple are two of the biggest names in online services (some others being Twitter, Meta, and Amazon). When it comes to account authentication, they offer some key advantages that are hard to match:

1. A massive, reliable infrastructure. It's very rare Google or Apple 'go down', and when that does happen, it's usually due to some other, bigger issue such as a major Cloudflare outage.
2. Incredibly high security. Both these platforms manage massive amounts of very valuable data and have become very good at keeping that data secure.
3. Easy to implement authorisation API. It's very easy (relatively speaking) to implement Google or Apple authentication very securely into your site, which is why you see it in so many places.
4. Massive, well maintained databases. It would be almost impossible for your user register to run out of space on these systems, and because these systems are being used for a whole host of other, even higher value services, they're very well maintained.
5. Native integration into their ecosystems. The D&D Beyond app is available on android and iOS, meaning that these authentication methods naturally integrate into a users own accounts on whatever device they may be running the app, allowing them to make use of Apple or Google Pay for purchasing content.
6. Registration convenience. Users don't have to enter a bunch of information, it's all pulled (securely) from their Google/Apple account.

Ultimately, it would be quite impossible for a website to design and build their own authentication system that comes even remotely close to Apple or Googles in terms of reliability and security, two things you really want from authentication. And that's not even touching on the convenience factors.

Quote from Davyd >>

I believe I explained this to you before in a different thread.

Google and Apple are two of the biggest names in online services (some others being Twitter, Meta, and Amazon). When it comes to account authentication, they offer some key advantages that are hard to match:

1. A massive, reliable infrastructure. It's very rare Google or Apple 'go down', and when that does happen, it's usually due to some other, bigger issue such as a major Cloudflare outage.
2. Incredibly high security. Both these platforms manage massive amounts of very valuable data and have become very good at keeping that data secure.
3. Easy to implement authorisation API. It's very easy (relatively speaking) to implement Google or Apple authentication very securely into your site, which is why you see it in so many places.
4. Massive, well maintained databases. It would be almost impossible for your user register to run out of space on these systems, and because these systems are being used for a whole host of other, even higher value services, they're very well maintained.
5. Native integration into their ecosystems. The D&D Beyond app is available on android and iOS, meaning that these authentication methods naturally integrate into a users own accounts on whatever device they may be running the app, allowing them to make use of Apple or Google Pay for purchasing content.
6. Registration convenience. Users don't have to enter a bunch of information, it's all pulled (securely) from their Google/Apple account.

Ultimately, it would be quite impossible for a website to design and build their own authentication system that comes even remotely close to Apple or Googles in terms of reliability and security, two things you really want from authentication. And that's not even touching on the convenience factors.

 
Ah, yes sorry.  

I remember now.  A while ago I asked a question about why we couldn’t sign up directly.  

Sorry, it was some time ago and it wasn’t until you mentioned it that I remembered and went back to read the responses to that question.  

I was hoping that integration with a wizards account was possible now, but from what you say, it doesn’t look like that will happen.  Not to worry, D&D Beyond will just have to remain connected to my AppleID.  

I just worry about having my AppleID used in so many places.  

Again, sorry for asking that same question.  I really had forgotten.  

You can always just make a new Apple ID or Google account just for D&D Beyond.

If you're worried about security (they crack one, they crack all), then creating an extra account mitigates that. However, it can get unwieldy, there are a lot of sites that use Google authentication. Many have a wider range than DDB (they use FB, Twitter, etc), but still. Eventually you get to the problem that you then have to remember which site associates with what ecosystem, then which identity in that ecosystem...it gets messy. For me, it's much easier to have usernames and passwords. I have a system going to it's easy to remember. Unfortunately, the ecosystem route seems to be becoming more and more common.

I'm also concerned as to what and how much data sites like DDB can access from my ecosystem. I'm finding a lot of intrusive stuff on there, and I'm not sure I'm happy DDB (or the various other sites) having access to it.

Quote from Linklite >>

I'm also concerned as to what and how much data sites like DDB can access from my ecosystem. I'm finding a lot of intrusive stuff on there, and I'm not sure I'm happy DDB (or the various other sites) having access to it.

 As I understand it, OAuth (the protocol in use here) doesn't give DDB access to anything from the authenticating site; it's just a protocol to let them securely ask google/apple/whoever "this person says they're user@whoever. Are they?"