Open Street Map

http://www.openstreetmap.org

OpenStreetMap is built by a community of mappers that contribute and maintain data about roads, trails, cafés, railway stations, and much more, all over the world.

Local Knowledge

OpenStreetMap emphasizes local knowledge. Contributors use aerial imagery, GPS devices, and low-tech field maps to verify that OSM is accurate and up to date.

Community Driven

OpenStreetMap’s community is diverse, passionate, and growing every day. Our contributors include enthusiast mappers, GIS professionals, engineers running the OSM servers, humanitarians mapping disaster-affected areas, and many more. To learn more about the community, see the user diaries, community blogs, and the OSM Foundation website.

Open Data

OpenStreetMap is open data: you are free to use it for any purpose as long as you credit OpenStreetMap and its contributors. If you alter or build upon the data in certain ways, you may distribute the result only under the same licence. See the Copyright and License page for details.

Partners

Hosting is supported by the UCL VR Centre, Imperial College London and Bytemark Hosting, and other partners.

 

Wolfram Alpha

WolframAlpha_logo

Wolfram Alpha search – is a great tool – for instance you can enter a date/time in future and it will calculate how many days to that day.

just put “date to” followed by date in words or numbers.

you can also ask it lots of other stuff:

 

 

https://www.wolframalpha.com/

RSA Authentication Manager 8: Move users across Identity Sources

AM8.x—Migrating users across Identity Sources

1.-In this example I have 10 users (test1-10) in an external Identity Source pointing to a Windows 2003 AD server. All 10 users have tokens assigned and PINs created. One of the users also has a replacement token assigned (but haven’t used it yet).

2.-To make things easier I create a group in AM called export. I assigned the users from the 2003 AD that I wanted to migrate (test1-test10) to a different Identity Source and placed them in this group. It is possible to just export all users with tokens as well.

3.-To Export the users we first need to download the encryption key: go to Administration—Export/ Import Tokens and Users—Download Encryption Key.

Save the file to a desired location.

4.-Now to actually export the users: go to Administration—Import/Export Tokens and Users—Export Tokens and Users (refer to screenshot from above).

5.-Browse to the encryption key you downloaded and select Users with Tokens (Users without tokens will not be exported) for the Export option and Click Next:

6.-On the next screen under Filter User with Tokens By Group I selected Narrow the selection by group membership. I typed the group, export, that I created for this which has the desired users and hit Search.

Select the group and then hit the > bring the group over on the right side under the Selected Groups section. Check the box next to the group and click Export:

7.-This brings you to the Import/Export Status screen. Once it’s complete download the file. I saved it in the same directory that I saved the encryption file.

8.-Now we have to remove the users that we exported and cleanup the database. Since I no longer need the 2003 Identity Source I’m going to unlink it.

Security Console—Setup—Identity Sources– Link Identity Source to System. I unlinked the 2003 ID source and clicked Save:

9.-Confirm that you want to unlink the Identity Source on the subsequent screen and make sure to check the box, then click on Unlink:

10.-Now we want to run the Scheduled cleanup job. Security Console—Setup—Identity Sources—Scheduled cleanup:

I set mine to run a few minutes from now and click Save:

11.-You can monitor the progress using the real-time system monitor or under Administration Batch jobs. Once the cleanup has completed login to the Operations Console and delete the Identity Source you just unlinked.

Deployment Configuration—Identity Sources—Manage Existing. Enter your Superadmin credentials when prompted. Now click the little arrow next to the ID source you wish to remove and select Delete:

12.-On the following screen check the box for Yes, delete the identity source and click Delete Identity Source.

13.-I’m going to be importing the users that were exported into a 2008 domain. The first name, last name, and default login all match what was in 2003. The 2008 Identity Source is already setup in AM8 and linked via the Security Console.

14.-Now to import the users that were exported. Security Console–Administration—Import/Export Tokens and Users—Import Tokens and Users. Select the .pkg file that you created during the export and click Next.

15.-For Security Domain I’m keeping the default of System Domain and clicking Next:

16.-On the subsequent screen you select the Identity Source that you wish to import to and then click Next:

17.-Review the summary which should match the export summary and click Import:

18.-Once it completes you should get something like the following:

***FYI, You will get the Done with Warning status as well.

19.-The imported users should now show up in the new Identity Source with their tokens/PINs intact. I was able to login successfully with the migrated accounts and Pins were retained.