Legacy Google Apps Changing Domain Alias to Primary Domain - google-apps

I have signed up earlier for the google apps account which is now called as legacy and the primary domain has got expired. I am trying to bootstrap a startup ourselves and thought of using this legacy account. below are the steps I tried so see if I can change the primary domain. let me know if anyone of you know about any existing solutions.
No option to add a secondary domain because its a legacy account. Google removed the option.
Added our new domain as a domain alias.
Went through the GAM tool, Admin SDK.
There are couple of options which I could think off to achieve this.
Upgrade the google legacy account to a 30 day trial account and get the option to add a secondary domain and then make the primary domain change and downgrade. However, from what I have read in the internet, there is a risk where when I downgrade there would be only 1 license to use.
https://www.isaumya.com/how-to-change-primary-domain-for-google-apps-legacy-account/ here is a website telling me they have a script to run and make these changes and asking for 30 dollars.
https://github.com/marcelobern/Google-Admin-SDK-Domain This is another option that I came across.
I know it a sounds a bit crude but I am just trying to use a freebie till we get a funding for the startup :) Let me know if anyone of you have any solutions.

If you do the free trial, you will gain the ability to add a domain rather than a domain alias. However, you will not be able to downgrade back to legacy free until you remove the domain. (I tried this on an account I was willing to lose).
For your purposes I think you could get away with using the domain alias. Your users will need to sign in under the old primary domain name but your users can configure your domain alias as the default outgoing email address under settings/Accounts/Send mail as.

Related

How does one get around the firebase hosting proof of ownership catch 22?

Firebase hosting requires that a TXT setting be set up to as they call it
Prove the domain is yours
I purchased a domain. It is mine. In order to set this TXT setting I have to have the domain hosted. The place I purchased the domain from sells hosting for minimum one year at a time. What is the point of firebase hosting when I have to buy hosting somewhere in order to prove that the domain is mine? Is there any way to get around this catch 22?
Proving ownership is done by putting a TXT record in the DNS. This doesn't require that you have a website hosted yet, it merely requires access to the DNS settings for your domain.
It's hard to help beyond that without knowing where you registered your domain.
Update. I took Frank's advice and set up a few Namecheap accounts. Wowie! The discount names are as cheap as 50 cents/year if you buy 1 or 5 years. Thanx for the advice. There is a caveat to using Namecheap/firebase, however.
Do not take this as if I were looking a gift horse in the mouth. I am super grateful to Google for free hosting. I merely want to warn users that firebase is not a free country. Google forces the s religion. I put in many hours of work to create my website using my girlfriend's hosting MySQL. Her hosting platform does not have an s in the URL: https. So the Angular 5 HTTP calls barf. I also included a contact page and a share via email popup. I used my girlfriend's hosting and set up a poor man's PHP web service for that. That does not work because girlfriend's hosting uses HTTP not https. So now I have to go back and recode these backend connections to use Google firebase and Google functions/SendGrid. I could have done that from the get-go and saved myself the time and aggravation.

Redirect my weebly site to my heroku app

I recently acquired a domain while buying a logo and some business cards through logomaker.com. I took this opportunity to claim the domain that I want to use for my rails app on heroku (Was this a mistake?).
Currently I seem to be required to use Weebly to edit the site for this new domain (But I'm thinking about transferring the domain to my GoDaddy account for simplicity. Is this a good idea?) I'm trying to route the simple domain to my rails app. In other words, I want users to be able to type mrzschool.com and get routed to mrzschool.herokuapp.com. I haven't been able to find a way to do this through Weebly.
I also have access to DNS and nameserver settings, such as imap and pop, through logomaker.com. This seems like it might be a way to change the routing, but I'm realizing that I'm unschooled in the realm of domains and DNS.
I'd suggest you go through the the process of moving your domain registrar from logomaker to your goDaddy account, were you can keep an eye on this domain along side any other domains you've there. It's a tedious process but worth it in my opinion. However, it's optional since you have all the control you need to do that via logomaker.
The heroku docs mentions (found here) how you can point your own custom domain to your heroku app subdomain. Keep in mind that you will need to verify your account and your ownership of the domain.
You will also find some useful troubleshooting steps here.

Limiting the number of logins by ip address in moodle

Am using Moodle for online quizzes locally in a lap environment.
I am facing a problem with students sharing log in credentials in the exam. so am searching for a solution that will associate every user with a single ip address for a period of time. is there is any way from moodle to do this.
This may not be possible to completely prevent without writing a new plugin to cache the login and restrict any new logins for a period of time. IP address probably isn't the best way to do this, as multiple students could be using the same IP address if sharing something like a WiFi connection at a campus or public location.
However, you can make it a little more difficult.
1.) Enable the "Limit concurrent logins" setting. You can find this in Site Administration > Plugins > Authentication > Manage Authentication.
2.) Try this plugin. It will cache login information for a student when accessing a quiz and prevent another computer from logging in to the same account from continuing that same quiz.
3.) Use some sort of single-sign-on service which you can connect with Moodle via a SAML2 plugin like this one. Look for a service that provides the specific functionality you're asking for.
4.) Use multi-factor authentication. You can combine this with option #3 above or look for a plugin supported by your current version of Moodle. Lambda Solutions appears to have a commercial product for this. There is also an older plugin on Moodle's site that you could get a developer to update for you.

How to Configure IdentityManager

I'm at the early days of looking into IdentityServer v3 and IdentityManager, as I'm certain those guys are more clued up than I, but I cannot see how to configure the IdentityManager.
If we're deploying IdentityManager to a client, all the client want to do is "standard admin type stuff", such as
create users
unlock accounts (e.g. after 3 failed login attempts)
suspend accounts (not paid your bill, tut tut...)
delete users
..rather than amend claims, roles and suchlike (presumably these would be hidden from the Administrators).
What am I missing?
Or, is the IdentityManager supposed to be used by the implementation team installing the thing, and then the business administrators who deal with the topics listed above actually don't use IdentityManager at all, but a separate admin site we have to write? As far as I can make out all the pages, htm letc is within the nuget package so cannot be amended by me.
If it makes any difference, we're trying to create a public facing website that can be logged into, but the users are only created by the company, whose admin site to create & administer the users is IP restricted / not public facing.
Identity Manager is aimed at developers and internal administrators for testing and initial configuration purposes, as opposed to end users.
Check out https://vimeo.com/125426951 by the repo's author. I think it's explicitly stated at around the 1 minute mark. It's mentioned on the Github issue tracker quite frequently too.
Also, it's not that extensible yet, so you won't be able to brand it or remove sections (such as your requirement of no claims).

AWS Route 53 email setup with EC2 OR webmail/email service provider

I bought domain names on AWS Route53.
I launched the websites on S2.
Now, I cannot setup new email addresses.
SES/EC2 are ready-to-go solutions.
I want to:
Create new email addresses ASAP (business trip in 10 days)
Simple daily-email, no newsletters, no mass emails
Ready-to-go solution, no installing/configuring of complex technical systems like Linux, Ubuntu, SquirrelMail, Google Apps systems...
I was referred by a MX record based system used by Outlook; unfortunately this service is no longer available.
Questions:
Is there any easy and simple solution using Route 53/SES/EC2 ?
Or, any 3rd party service that I can use ? (ideally, something free – I do not want to pay 50$/year per user)
There is a pretty straight-forward free service that I'm using called Zoho:
https://www.zoho.com/mail/
I'm new to it as well, so I can't speak to its reliability, but setup is pretty easy. It will have you verify your account by creating a record set in your 'Hosted Zone' page in Route 53.
for creating webmail there's a WorkMail option on aws services. you can create an email account there.
first click on add organization button . then go to quick setup. fill the requirements. after it's done click on the organization name that you already created and create a user.
enter a username and password that you want. after creating user , you can find the webmail url on "organization setting tab".
the WorkMail can integrates nicely with SES.