text:
MidPoint 4.0.4 "Gutenberg" Update 4
Release 4.0.4 is a thirty-eight midPoint release. It is the fourth maintenance update for 4.0.x version family code-named Gutenberg. The 4.0.x is a long-term support (LTS) version family. The 4.0.4 release brings bugfixes and improvements for upgrade to 4.4 LTS.
Release date | 14 December 2021 |
Release type | Maintenance release (LTS) |
End of support | 08 September 2022 |
Johannes Gutenberg (c.1400 - 1468) was German blacksmith, goldsmith, printer and publisher who introduced printing to Europe with the printing press. Information sharing that was enabled by printing caused a cultural and scientific revolution. Modern period of human history was born. The effect of Gutenberg's inventions can hardly be overstated. However, it was not just the printing press itself that made a difference. Gutenberg created entire printing system: the press, adjustable molds, oil-based ink, mechanical movable type and the alloy for casting the type. Those simple elements combined together to create an efficient and economically feasible system for producing books. Similarly to Gutenberg's printing system, midPoint 4.0 is a revolutionary release. It bring a couple of long-awaited features. However what really matters is a huge amount of improvements and smaller features. Those are designed to work together with existing midPoint features to create a comprehensive and consistent system for identity management and governance. There are also numerous internal improvements and cleanups that enable a long-term maintenance of midPoint 4.0. |
Changes With Respect to Version 4.0
New Features, Improvements and Bugfixes
Archetype assignments are always active, regardless of the lifecycle state.
Audit log viewer improvements
Option to disable count on pages that list objects.
"skip model processing" option in asynchronous updates
Info/Env/Health/Metrics/ThreadDump/HeapDump endpoints
Chaining of mappings provided by assignments
Support for migration <account> → <shadow>
Override of "help" in object template
assignmentPath variable in approverExpressions
Tomcat 9 support
PostgreSQL 11 support
Numerous bugfixes
Schema annotations for upgrade to midPoint 4.4 LTS "Tesla"
Deprecation, Feature Removal And Incompatible Changes
Support for eDirectory was removed. eDirectory support was a maintenance burden. There is currently no subscriber using eDirectory connector, therefore the code of eDirectory connector was removed from the LDAP connector bundle.
Support for BEA/Oracle WebLogic deployment was removed. Weblogic support was maintained because of a special arrangements with one of the first midPoint subscribers. Weblogic support is not needed by that subscriber and it is not used by any other subscriber. Therefore support for Weblogic deployment is no longer available. Tomcat is now the only supported web container. Support for any other containers is not planned.
The #selfRequestAssignment GUI authorization is deprecated. It does not provide any access. The #selfRequestAssignments authorization provides access to all assignment shopping cart pages.
Microsoft Windows Server 2008R2 and Active Directory 2008R2 is no longer supported for new midPoint installations. Those servers may be supported under some circumstances for customers that purchased midPoint subscription before release of midPoint 4.0.2. Please contact Evolveum sales for the details.
Support for .NET remote connector server is deprecated.
Changes With Respect to Version 3.9
New Features and Improvements
Major features
Support for multiple equivalent accounts on a resource (inbound)
Thresholds and limits (experimental)
Approvals without a workflow engine
User interface improvements
Dashboards and status reports (experimental)
Shopping cart improvements
Reworked "projections" tab
Ability to set custom name for midPoint
Case management improvements (experimental)
Session management page
Minor user experience improvements
Security improvements
Expression Profiles (limited implementation)
Request identifier in the audit log
Numerous security fixes from the EU-FOSSA bug bounty (see Security Advisories)
Support for custom columns in audit table (experimental)
Support for PolyStrings all the way to the connector (experimental)
Asynchronous (messaging) connector options (prototype)
Improved shadow consistency with
property -
Support for seach hierarchy scope
Miscellaneous improvements
Mapping range pre-defined sets
Mapping state properties
Support for populate expressions in autoassignments
Task management in cluster is using REST
Autogenerated node identifier in a cluster
Support for attachments in mail notifications
Whitelists for notifications
Support for expression in mapping time constraints
Partial support for polystring "lang" and translations (experimental)
Miscellaneous clustering improvements
Many improvements in reconciliation and synchronization tasks
Improved Prism API and code structure
Improved GUI interfaces and code structure
Long-term support stabilization
Java 11 support
New internal engine for policy-based approvals (replaces Activiti BPM)
Cluster management is using REST instead of JMX
Numerous performance and scalability improvements
Deprecation, Feature Removal And Incompatible Changes
Support for Java 8 is deprecated. Running midPoint on OpenJDK 8 is supported for midPoint 4.0 and the preliminary plan is to support for the usual lifetime of ordinary support of midPoint 4.0.x line (which means 3 years). But Java 8 support may be shortened, e.g. in case that Oracle or OpenJDK project will stop providing updates to Java 8 platform. It is strongly recommended to upgrade to Java 11 as soon as possible.
Support for Oracle Java builds is limited (see below).
Support for PostgreSQL 9.5 (9.5, 9.5.1) is deprecated.
Support for Microsoft SQL Server 2014 is deprecated.
SOAP-based IDM Model Web Service Interface is deprecated. It will no longer be maintained and it will be completely removed in future versions. Please use RESTful interface instead.
As SOAP interface is deprecated, the example SOAP client (
component) was removed from midPoint source code. It will no longer be maintained. -
There are many schema changes, including many incompatible schema changes. Please see the upgrade section below for the details.
Activiti BPM that was used as "workflow engine" was removed from midPoint.
Support for BEA/Oracle WebLogic (12c) is deprecated and it is no longer available as a public feature. Artifacts for weblogic support will be removed as soon as such action is confirmed with the affected subscribers.
Releases Of Other Components
New versions of LDAP Connector and Active Directory Connector were released during the course of midPoint 4.0 development. There were major improvements and fixes in those connectors. See the connector pages for the details. MidPoint 4.0 contains most recent versions of those connectors.
New versions of CSV Connector and DatabaseTable Connector were released during the course of midPoint 4.0 development. There were minor improvements and fixes in those connectors. See the connector pages for the details. MidPoint 4.0 contains most recent versions of those connectors.
MidPoint plug-in for Eclipse IDE was updated and released during the course of midPoint 4.0 development. The correct version of the plugin to use with midPoint 4.0 is 0.10.8.
Official release of Java REST client is planned shortly after midPoint 4.0 release.
Release of overlay projects and other associated artifacts is planned after 4.0 release.
Other Major Changes And Limitations
There was a change in MidPoint 4.0 licensing. MidPoint 4.0 is dual-licensing under Apache License and EUPL. Which means that the users of midPoint may choose any of those licenses. Therefore there is almost no change for existing midPoint users that used midPoint under the terms of Apache License. The only effect of this change is the change in code contribution process that requires signing of CLA. Some parts of midPoint such as samples and localizations that are more intense in contributions are still single-licensed under the terms of Apache License to simplify contribution process. Those parts have been separated into their own projects.
The structure of midPoint reporting service was changed during the course of midPoint 4.0 development. Those changes were motivated mostly by security concerns. There are incompatible changes, therefore existing versions of midPoint plugin for JasperSoft studio will not work with midPoint 4.0. The future of JasperSoft studio integration with midPoint is currently being debated internally in midPoint teams. Platform subscribers that currently use or plan to use JasperSoft studio are invited to provide their feedback and opinions. The result will be either new release of the integration component or deprecation of JasperSoft studio integration.
See upgrade instructions below for more details.
Purpose and Quality
Release 4.0.4 LTS (Gutenberg Update 4) is intended for full production use. It belongs to a long-term support (LTS) family, supported for a prolonged time period. Therefore it is intended for users that prefer long-term stability over new features.
All features are stable and well tested - except the features that are explicitly marked as experimental or partially implemented. Those features are supported only with special subscription contract.
Functionality that is marked as EXPERIMENTAL is not supported for general use (yet). Such features are not covered by midPoint support. They are supported only for those subscribers that funded the development of this feature by the means of platform subscription or for those that explicitly negotiated such support in their support contracts.
MidPoint comes with bundled LDAP Connector. Support for LDAP connector is included in standard midPoint support service, but there are limitations. This "bundled" support only includes operations of LDAP connector that 100% compliant with LDAP standards. Any non-standard functionality is explicitly excluded from the bundled support. We strongly recommend to explicitly negotiate support for a specific LDAP server in your midPoint support contract. Otherwise only standard LDAP functionality is covered by the support. See LDAP Connector page for more details.
MidPoint comes with bundled Active Directory Connector (LDAP). Support for AD connector is included in standard midPoint support service, but there are limitations. Only some versions of Active Directory deployments are supported. Basic AD operations are supported, but advanced operations may not be supported at all. The connector does not claim to be feature-complete. See Active Directory Connector (LDAP) page for more details.
MidPoint comes with bundled Active Directory Connector (LDAP), which includes support for PowerShell scripting. This scripting is supposed to be used to supplement creation of Active Directory (windows) accounts by using simple scripts. It is not supposed to be used to manage Microsoft Exchange accounts. Management of Exchange accounts can be quite a complex matter, requiring complicated PowerShell scripts. Support for the use of this connector to manage Exchange accounts has to be purchased separately.
The PowerShell capability of Active Directory Connector (LDAP) will be migrated to a dedicated connector in midPoint 4.1 or later. Once this capability is migrated, PowerShell scripting will no longer be supported as part of bundled midPoint connectors. There will be special connector for that purpose and support for such connector will be sold separately. Therefore, if you need support for PowerShell scripting, we recommend explicitly negotiating such support in your midPoint support contract. MidPoint subscribers that purchased their full subscription before the release date of midPoint 4.0 should not be affected by this change. However we recommend to check status of your subscription coverage by contacting Evolveum.
There is an option to modify midPoint to support LDAP and CAS authentication by using Spring Security modules. This method is used in several midPoint deployments. However, such authentication modules are not officially supported as part of usual midPoint subscriptions. Only community-level support is provided for those modules. Commercial-grade support for this authentication method is available, but it has to be explicitly negotiated in a subscription contract.
MidPoint user interface has flexible (fluid) design and it is able to adapt to various screen sizes, including screen sizes used by some mobile devices. However, midPoint administration interface is also quite complex and it would be very difficult to correctly support all midPoint functionality on very small screens. Therefore midPoint often works well on larger mobile devices (tablets) it is very likely to be problematic on small screens (mobile phones). Even though midPoint may work well on mobile devices, the support for small screens is not included in standard midPoint subscription. Partial support for small screens (e.g. only for self-service purposes) may be provided, but it has to be explicitly negotiated in a subscription contract.
There are several add-ons and extensions for midPoint that are not explicitly distributed with midPoint. This includes midPoint plug-in for Eclipse IDE, extension of Jasper studio, Java client library, various samples, scripts, connectors and other non-bundled items. Support for these non-bundled items is limited. Generally speaking those non-bundled items are supported only for platform subscribers and those that explicitly negotiated the support in their contract. For other cases there is only community support available. For those that are interested in official support for IDE add-ons there is a possibility to use subscription to help us develop midPoint studio (MID-4701).
The integration of Jaspersoft Studio for midPoint (a.k.a. "Jasper plugin") will not work with midPoint 4.0. The reporting web service was changed and the plugin was not yet adapted to that change. This work is planned for later. The priorities will be determined by platform subscribers.
MidPoint contains a basic case management user interface. This part of midPoint user interface is not finished. The only supported part of this user interface is the part that is used to process requests and approvals. Other parts of case management user interface are considered to be experimental, especially the parts dealing with manual provisioning cases.
MidPoint is known to work well in the following deployment environment. The following list is list of tested platforms, i.e. platforms that midPoint team or reliable partners personally tested with this release. The version numbers in parentheses are the actual version numbers used for the tests.
It is very likely that midPoint will also work in similar environments. But only the versions specified below are supported as part of midPoint subscription and support programs - unless a different version is explicitly agreed in the contract.
Support for some platforms is marked as "deprecated". Support for such deprecated versions can be removed in any midPoint release. Please migrate from deprecated platforms as soon as possible.
OpenJDK 11 (11.0.4). This is a recommended platform.
OpenJDK 8 (1.8.0_221) DEPRECATED
OpenJDK 11 is a recommended Java platform to run midPoint.
Support for Java 8 is deprecated. Running midPoint on OpenJDK 8 is supported for midPoint 4.0 and the preliminary plan is to support for the usual lifetime of ordinary support of midPoint 4.0.x line (which means 3 years). But Java 8 support may be shortened, e.g. in case that Oracle or OpenJDK project will stop providing free updates to Java 8 platform. It is strongly recommended to upgrade to Java 11 as soon as possible.
Support for Oracle builds of JDK is provided only for the period in which Oracle provides public support (free updates) for their builds. End of free updates for Oracle JDK 11 were planned for March 2019, and the current status is not known. Which means that Oracle JDK 11 may not be supported at all for MidPoint 4.0. MidPoint is an open source project, and as such it relies on open source components. We cannot provide support for platform that do not have public updates as we would not have access to those updates and therefore we cannot reproduce and fix issues. Use of open source OpenJDK builds with public support is recommended instead of proprietary builds.
Web Containers
MidPoint is bundled with an embedded web container. Stand-alone deployment is default and recommended deployment option. See Stand-Alone Deployment for more details.
In addition to that, midPoint 4.0.x can be explicitly deployed into a web container. Apache Tomcat is supported as the only web container for midPoint. Support for no other web container is planned. Following Apache Tomcat versions are supported:
Apache Tomcat 8.5 (8.5.31), 9.0 (9.0.24)
Apache Tomcat 8.0.x is no longer supported as its support life is over (EOL).
MidPoint supports several databases. However, performance characteristics and even some implementation details can change from database to database. Since midPoint 4.0, PostgreSQL is the recommended database for midPoint deployments.
H2 (embedded). Supported only in embedded mode. Not supported for production deployments. Only the version specifically bundled with midPoint is supported.
H2 is intended only for development, demo and similar use cases. It is not supported for any production use. Also, upgrade of deployments based on H2 database are not supported. -
PostgreSQL 11 and 10. This is the recommended option. Support for PostgreSQL 9.5 (9.5, 9.5.1) is deprecated.
MariaDB (10.0.28)
MySQL 5.7 (5.7)
Oracle 12c
Microsoft SQL Server 2016 SP1. Support for SQL Server 2014 is deprecated.
Our strategy is to officially support the latest stable version of each database (to the practically possible extent). It may be possible to support also older database versions. But as that means additional testing and support effort, we provide such service only with special support contracts. Contact Evolveum sales for the details.
Only a direct connection from midPoint to the database engine is supported. Database and/or SQL proxies, database load balancers or any other devices (e.g. firewalls) that alter the communication are not supported.
Supported Browsers
Firefox (any recent version)
Safari (any recent version)
Chrome (any recent version)
Opera (any recent version)
Microsoft Internet Explorer (version 9 or later)
Recent version of browser as mentioned above means any stable stock version of the browser released in the last two years. We formally support only stock, non-customized versions of the browsers without any extensions or other add-ons. According to the experience most extensions should work fine with midPoint. However, it is not possible to test midPoint with all of them and support all of them. Therefore, if you chose to use extensions or customize the browser in any non-standard way you are doing that on your own risk. We reserve the right not to support customized web browsers.
Microsoft Internet Explorer compatibility mode is not supported.
Important Bundled Components
Component | Version | Description |
Tomcat |
9.0.24 |
Web container |
ConnId |
184.108.40.206 |
ConnId Connector Framework |
LDAP connector bundle |
2.3 |
LDAP, Active Directory and eDirectory connector |
CSV connector |
2.3 |
Connector for CSV files |
DatabaseTable connector |
22.214.171.124 |
Connector for simple database tables |
Download and Install
Release Form | Download | Install Instructions |
Binary |
https://evolveum.com/downloads/midpoint/4.0.4/midpoint-4.0.4-dist.zip |
Source |
Java API JavaDoc |
https://www.evolveum.com/downloads/midpoint/4.0.4/midpoint-api-4.0.4-javadoc/ |
SchemaDoc |
https://www.evolveum.com/downloads/midpoint/4.0.4/midpoint-4.0.4-schemadoc/ |
MidPoint is software that is designed for easy upgradeability. We do our best to maintain strong backward compatibility of midPoint data model, configuration and system behavior. However, midPoint is also very flexible and comprehensive software system with a very rich data model. It is not humanly possible to test all the potential upgrade paths and scenarios. Also some changes in midPoint behavior are inevitable to maintain midPoint development pace. Therefore we can assure reliable midPoint upgrades only for midPoint subscribers. This section provides overall overview of the changes and upgrade procedures. Although we try to our best it is not possible to foresee all possible uses of midPoint. Therefore the information provided in this section are for information purposes only without any guarantees of completeness. In case of any doubts about upgrade or behavior changes please use services associated with midPoint subscription or purchase professional services.
Major Release 4.0
Even though midPoint minor releases are managed with almost complete compatibility in mind, midPoint 4.0 is different. MidPoint 4.0 is a major release. This is a point in midPoint development lifecycle when we remove obsolete functionality and when we make major updates to midPoint schema, database data structures and functionality. Every experienced software engineers know that it is rarely feasible to make such changes while keeping compatibility as the same time. Therefore midPoint 4.0.x is not backwards-compatible with midPoint 3.x. But the situation is not as bad as it might seem. We have tried to avoid changes that were not necessary. Therefore vast majority of midPoint data schema is still compatible. It is just those little places where it is not. Those places are the cause that we cannot declare complete compatibility. And that is also the reason that there is no automatic upgrade path from midPoint 3.x that is 100% reliable.
The changes in midPoint schema and functionality is mostly limited to data items that were already deprecated for a long time, some of them going back even to midPoint 2.x. Those elements were removed or significantly changed.
All such changes were marked as "planned removal in 4.0" in midPoint 3.9 schema.
This plan was documented in midPoint 3.9 release notes therefore the users had sufficient time to prepare.
You should be able to upgrade without any major issues if you haven't used any deprecated properties or if you have avoided the use of removed elements at the very least.
But even in that case there may be some updates that need to be done manually.
Please refer to the section that deals with midPoint schema for details.
Please be especially careful about the iterationSpecification
element described below.
Upgrade from midPoint 4.0
Both midPoint 4.0.4 data model (schema) and database schema are compatible with midPoint 4.0. No special migration steps are needed to migrate the data. Upgrade of software packages is enough to upgrade to midPoint 4.0 to midPoint 4.0.4.
Upgrade from midPoint 3.x
Upgrade path from MidPoint 3.x goes through midPoint 3.9. Upgrade to midPoint 3.9 first by using the documented upgrade techniques. Then upgrade from midPoint 3.9 to 4.0.
Upgrade from midPoint 3.9
MidPoint 3.9 data model is not completely backwards compatible with previous midPoint versions. However, vast majority of data items is compatible. Therefore the usual upgrade mechanism can be used. The usual SQL scripts for database schema upgrade are provided. There are some important changes to keep in mind:
There were numerous schema changes that are described below.
Version numbers of some bundled connectors have changed. Therefore connector references from the resource definitions that are using the bundled connectors need to be updated.
Schema changes since 3.9
MidPoint schema was significantly changed since midPoint 3.9. There are many elements that are removed. Those were marked "for removal" in midPoint 3.9. Our Ninja tool can be used to detect the use of those elements even in midPoint 3.9. The "ninja" should be used to audit your use of deprecated data items before attempting to upgrade to midPoint 4.0.
However, there were also changes that were not foreseen at the time of midPoint 3.9 release or changes that cannot be easily detected by the means of our schema language. Those changes must be done manually either before upgrade or the configuration should be fixed after the upgrade:
Element iteration in object template was renamed to iterationSpecification. This change was needed due to major changes in midPoint object type hierarchy, somehow related to archetypes functionality. Object tempaltes need to be updated manually after the upgrade. The upgrade process will most likely remove the
element from object template and replace it with an integer value. Iteration specification element needs to be manually re-added asiterationSpecification
after the upgrade. The trouble is that there is no warning about this happening. Attempt to add such warning were thwarted due to complex reasons related to schema processing and data parsing. This and the primaryIdentifierValue below are perhaps the only two really important issue to keep in mind when upgrading from midPoint 3.x to midPoint 4.0. -
New primaryIdentifierValue property in shadows. MidPoint 3.x had chronic problems with shadow duplication. In fact midPoint 3.x itself worked fine and bugs related to shadow duplication were quite rare and often limited to very exotic and parallel cases. However, it was very easy to make a configuration mistake that lead to shadow duplication. Duplicated shadows are a major issue in midPoint and they may lead to data inconsistencies that are difficult to resolve. Therefore midPoint 4.0 is introducing a mechanism that can limit shadow duplication on a database level. There is a new
property that maps directly to a database column and there is an unique index on that. Therefore a whole class of possible shadow duplication problems is eliminated. The problem is that each resource object type may have different identifiers, normalization rules and so on. Therefore the computation ofprimaryIdentifierValue
may be quite complex. This is beyond the possibilities of SQL migration scripts. Therefore midPoint 3.9 that was just upgraded to 4.0 will have null values forprimaryIdentifierValue
. Those values should be computed and stored by using shadow refresh task. -
Elements relation and activation in assignmentTargetSearch expressions were removed. Please use the
mechanisms instead. This would an ordinary deprecated and removal, however in this case there is one difference. The mechanism that detects deprecated and removed items will not detect this change. The cause of this is the fact, that expressions are not Prism containers, therefore midPoint schema-processing code does not have visibility inside those data structures. -
Element account can no longer be used as top-level element for shadow objects. Element
should be used instead. MidPoint was using the correctshadow
element for years and years. Therefore this should not be a significant problem during an upgrade unless there are some ancient manually-created shadows. MidPoint 4.0.4 will parse even the data withaccount
element, automatically converting them toshadow
. The data in the database should be cleared up when the shadow objects are updated (e.g. during reconciliation). -
Element userTemplate can no longer be used as top-level element for object template. Element
should be used instead. This situation is almost the same as theaccount
case above. -
Attribute ref is removed from resource synchronization section. Please use
element instead. Theref
attribute was deprecated even in midPoint 2.x. As this is an attribute and not an element then the automatic detector of removed elements does not work correctly in this case. The use ofref
attribute should be fixed before any attempts to upgrade to midPoint 4.0.
Other removed items are automatically detected by midPoint parsing code and such elements should be automatically removed from the data. There will be a warning in the log file in case that such an element was removed during parsing. Please note that it takes an update of the object to store the data value without the removed elements. MidPoint does not do it proactively.
Even though this is midPoint 4.0, the numbers in the schema namespaces are still referring to version 3, e.g. http://midpoint.evolveum.com/xml/ns/public/common/common-3
. This might seems strange and this decision was given a significant amount of consideration.
Version number was introduces to the namespaces in early days of midPoint when such a practice was quite common in the XML world.
However, the current consensus of midPoint architects is that the schema versioning mechanism in the XML namespace is far from being ideal.
A better versioning mechanism will be needed in the future.
The preliminary design is to remove version number from the namespace entirely and use explicit schema versioning that could reflect semantic versioning principles.
The preliminary plan is to address this in midPoint 5.0. Which would mean that the namespaces will need to change now and there will be another change in few years when midPoint 5.0 is released.
We have decided that the current change from "common-3" to "common-4" would not bring any significant advantage.
However, it would significantly complicate the upgrade from midPoint 3.x to midPoint 4.0. Therefore the decision was to keep the "common-3" namespaces.
Even though it might look strange, we are doing a very pragmatic decision here that makes midPoint migration much easier for everybody.
Prism API changes
Prism API changes are described in Upgrade to 4.0 - Prism API migration notes.
Upgrade process
Flowing steps are an outline of an upgrade process:
Back up your configuration and data.
Make sure that you are not using elements that are planned for removal. If they are used then reconfigure them to their new equivalents. It is recommended to do the same with all deprecated configuration elements.
Stop all tasks, disable end user access to user interface.
Shutdown midPoint.
Update midPoint distribution binaries.
Run database migration scripts.
Start midPoint. Make sure that tasks are stopped and end user access is disabled.
Update customized initial objects as needed.
element to object templates. -
Update connector references in the resources.
Run shadow refresh task to populate
in shadow objects. -
Mind the warnings in log files. There may be warnings about removal of deprecated items.
Test new configuration.
Start the tasks. Do it with caution. Start the tasks one-by-one, watch for any errors.
Re-enable user access to user interface.
Those steps are just a rough outline. Actual steps needed to upgrade to midPoint 4.0 may be different as the upgrade procedure depends on midPoint customizations, environment and other deployment details.
Changes in initial objects since 3.9
MidPoint has a built-in set of "initial objects" that it will automatically create in the database if they are not present.
This includes vital objects for the system to be configured (e.g. role superuser
and user administrator
). These objects may change in some midPoint releases.
But to be conservative and to avoid configuration overwrite midPoint does not overwrite existing objects when they are already in the database.
This may result in upgrade problems if the existing object contains configuration that is no longer supported in a new version.
Therefore the following list contains a summary of changes to the initial objects in this midPoint release.
The complete new set of initial objects is in the config/initial-objects
directory in both the source and binary distributions.
Although any problems caused by the change in initial objects is unlikely to occur, the implementors are advised to review the following list and assess the impact on case-by-case basis:* *
000-system-configuration.xml: Case and workitem views, expression profile, misc logging/tracing changes. Added two predefined tracing configurations.
010-value-policy.xml, 015-security-policy.xml: Removing deprecated elements
040-role-enduser.xml, 041-role-approver.xml: updates requires for new approval mechanisms. Allow End user to assign with default rel. only (MID-5592).
020-archetype-system-user.xml, 021-archetype-system-role.xml, 022-archetype-business-role.xml, 023-archetype-manual-provisioning-case.xml, 024-archetype-operation-request.xml, 025-archetype-approval-case.xml, 026-archetype-trace.xml: default archetype definitions
070-task-validity.xml: Update to current (non-deprecated) schema
090-report-audit.xml, 100-report-reconciliation.xml, 110-report-user-list.xml, 130-report-certification-definitions.xml, 140-report-certification-campaigns.xml, 150-report-certification-cases.xml, 160-report-certification-decisions.xml: Corrected encoding of Jasper report definition (it was base64-encoded twice), updating the definition to current schema (non-deprecated elements), updated report definition to reflect changes in Prism API
100-report-reconciliation.xml: Added option required for jasper report parameter (MID-5460).
130-report-certification-definitions.xml, 140-report-certification-campaigns.xml, 150-report-certification-cases.xml, 160-report-certification-decisions.xml: Fix for certification reports (MID-5811).
250-object-collection-resource-all.xml, 260-object-collection-task-all.xml, 270-object-collection-task-active.xml, 280-object-collection-resource-up.xml, 290-object-collection-audit-errors.xml, 300-object-collection-audit-modifications.xml, 330-object-collection-my-cases.xml: default object collections
310-dashboard-admin.xml: default system administration dashboard (experimental)
Bundled connector changes since 3.9
All bundled connectors were upgraded to the latest available version.
AD Connector was improved in several ways, including better support for userAccountControl attribute. It is recommended to refresh resource schema to take full advantage of those features.
Behavior changes since 3.9
Following expression variables are deprecated: user, account, shadow
Inbound mappings are evaluated together from all the resources, as they should. But do not rely on that (yet). Some resources may not be loaded.
Default range for inbound mappings has changed. Default range for single value items is "all", default range for multivalue items is "none". See Inbound Mapping page for the details.
Special authorization is needed to run reports (authorization-model-3#runReport). Access to report web service requires this authorization as well (e.g. needed for access by Jaspersoft Studio).
Change of
is not supported in midPoint 4.0. This functionality was never fully supported in midPoint 3.x either, even though some use-cases worked. Assubtype
is now deprecated, this functionality will not longer be supported. -
The #selfRequestAssignment GUI authorization is deprecated. It does not provide any access. The #selfRequestAssignments authorization provides access to all assignment shopping cart pages.
Public interface changes since 3.9
There were numerous changes to the IDM Model Interface (Java). Please see source code history for details. As this is a major release, there might be incompatible changes.
Prism interface was changes in many places. There is now a separate prism-api. However, this is not yet stable public interface. Changes to this API are expected in future midPoint versions. Although we will try to keep the changes compatible at least until the next LTS release, incompatible changes may happen occasionally.
IDM Model Web Service Interface (SOAP) is deprecated. The plan is to remove support for SOAP soon.
Important internal changes since 3.9
These changes should not influence people that use midPoint "as is". These changes should also not influence the XML/JSON/YAML-based customizations or scripting expressions that rely just on the provided library classes. These changes will influence midPoint forks and deployments that are heavily customized using the Java components.
Report API is changed, including the remote reporting inteface.
Variable typing and more strict checks. Which means that midPoint 4.0 is slightly less tolerant configuration errors.
There were numerous changes in internal code structure, most notably changes in Prism and GUI. Heavy customizations of midPoint 3.x are likely to break in midPoint 4.0.
Changes since midPoint 4.0
The #selfRequestAssignment GUI authorization is deprecated. It does not provide any access. The #selfRequestAssignments authorization provides access to all assignment shopping cart pages.
Initial object changes:
000-system-configuration.xml: Added two predefined tracing configurations.
040-role-enduser.xml: Allow End user to assign with default rel. only (MID-5592).
100-report-reconciliation.xml: Added option required for jasper report parameter (MID-5460).
130-report-certification-definitions.xml, 140-report-certification-campaigns.xml, 150-report-certification-cases.xml, 160-report-certification-decisions.xml: Fix for certification reports (MID-5811).
Known Issues and Limitations
As all real-world software midPoint 4.0.4 has some known issues. Full list of the issues is maintained in bug tracking system. As far as we know at the time of the release there was no known critical or security issue.
There is currently no plan to fix the known issues of midPoint 4.0.4 en masse. These issues will be fixed in future maintenance versions of midPoint only if the fix is covered by a support agreement or subscription. No other issues will be fixed - except for severe security issues that may be found in the future.
The known issues of midPoint 4.0.4 may or may not be fixed in following releases. This depends on the available time, issue severity and many variables that are currently difficult to predict. The only reliable way how to make sure that an issue is fixed is to purchase midPoint support. Or you can fix the bug yourself. MidPoint is always open to contributions.
This may seem a little bit harsh at a first sight. But there are very good reasons for this policy. And in fact it is no worse than what you get with most commercial software. We are just saying that with plain language instead of scrambling it into a legal mumbo-jumbo.
Some of the known issues are listed below:
Some of the changes related to approval cases are not shown (MID-5876)
There is a support to set up storage of credentials in either encrypted or hashed form. There is also unsupported and undocumented option to turn off credential storage. This option partially works, but there may be side effects and interactions. This option is not fully supported yet. Do not use it or use it only at your own risk. It is not included in any midPoint support agreement.
Native attribute with the name of 'id' cannot be currently used in midPoint (MID-3872). If the attribute name in the resource cannot be changed then the workaround is to force the use of legacy schema. In that case midPoint will use the legacy ConnId attribute names (icfs:name and icfs:uid).
Majority of the work on the Gutenberg release was done by the Evolveum team. However, this release would not be possible without the help of our partners, customers, contributors, friends and families. We would like to express our thanks to all the people that contributed to the midPoint project both by providing financial support, their own time or those that maintain a pleasant and creative environment for midPoint team. However, midPoint project would not exist without proper funding. Therefore we would like to express our deepest gratitude to all midPoint subscribers that made midPoint project possible.
Planned release dates are just that: they are planned. We do not promise or guarantee release dates. Software development is a creative activity that includes a lot of inherent risk. We are trying really hard to provide the best estimates. We are not able to provide precise dates for releases or deliveries. Do not rely on midPoint release dates. Plan your project properly to address the risk of delayed midPoint releases.
Planned scope of midPoint releases is also an estimate. MidPoint development process always includes the balancing of the iron triangle. Therefore planned release scope may change at any time. There is a method to make sure that midPoint releases will work well for your project and that method is platform subscription.
We do not make any claims that midPoint is perfect. Quite the contrary. MidPoint is a practical software, developed by living and breathing developers and deployed in a real world. There are both known and unknown issues in midPoint. Also, midPoint is not feature-complete. New features are introduced in midPoint all the time. But not all of them are completed. There are always some limitations. As the license states, midPoint is provided "AS IS". Please do not rely on midPoint functionality that you have not tested to make sure that it works. MidPoint support and subscription programs are a way how to handle those issues. But even with support service, do not rely on functionality that is not documented. If you plan to use undocumented or non-existing functionality, platform subscription is the right service for you.


text:
1/4 cup unsalted butter
3/4 cup all-purpose flour
3/4 teaspoon baking soda
1/2 teaspoon salt
1 1/4 cups quick oats
3/4 cup firmly packed brown sugar
1/2 cup creamy peanut butter
1 large egg
1 teaspoon vanilla extract
1/2 cup mini chocolate chips
Preheat oven to 375 degrees F. Grease cookie sheets.
Melt butter in a small saucepan over medium heat; continue to cook the butter, whisking frequently, until it starts to brown and foam, about 2-3 minutes. Set aside for 10 minutes.
In a medium mixing bowl, sift together flour, baking soda and salt; whisk in oats until combined.
In a large mixing bowl, using a mixer on medium speed, beat together brown sugar and peanut butter until creamy, about 1 minute; beat in browned butter until combined. Beat in egg and vanilla until combined. Reduce mixer speed to low and beat in oat mixture until combined; stir in chocolate chips.
Roll tablespoons of dough into balls, place on cookie sheets, and flatten slightly. Bake for 6-8 minutes or until golden brown around edges. Transfer to wire racks to cool.
Makes 4 dozen mini cookies

subset: commoncrawl


text:
Blake Shelton, Miranda Lambert + More to Headline 2012 Watershed Music Festival
In August, Blake Shelton, Miranda Lambert, Dierks Bentley, Sara Evans and plenty more will headline the first Watershed Music Festival to be held in George, Wash., just east of Seattle. The show, presented by Live Nation, is set for Aug. 3-5, and will give fans the full experience, with music, camping, late night sets, impromptu jam sessions, collaborations and more.
"The Gorge provides a feeling that is impossible to recreate anywhere else," says the show's co-promoter, and ACM Promoter of the Year, Brian O'Connell. "It is truly a magical place and provides the perfect setting for a cool, eclectic country event. We wanted to create something that didn't exist, from the caliber of artists to the camping and the atmosphere. I'm excited to be a part of it and see it all come together."
"In the storied 25 year history of the Gorge, we've been fortunate to host many of the nation's top country artists, but all have been single day concerts," adds Jeff Trisler, President of Live Nation Seattle. "For years, we've wanted to host a multiple day country festival that builds on the tremendous success for our annual Sasquatch Music Festival and Dave Matthews Band residency. We believe this event will bring that same sort of excitement and energy to the Gorge for an entirely new group of music fans."
Other confirmed artists scheduled to perform at the festival include Kix Brooks, Brantley Gilbert, Thompson Square, Uncle Kracker, Dwight Yoakam, Tracy Lawrence, Reckless Kelly, the Lost Trailers, Steve Holy, Johnny Reid, Jon Pardi, Thomas Rhett, Morgan Frazier and DeeJay Silver. The grounds will also have a local stage that will feature regional acts each night. More artists are set to be announced in the coming weeks.
Three-day festival passes start at only $90 and go on sale Sat., May 5 at Ticketmaster and Live Nation. For more information on the festival, visit its official website by clicking here. or follow them on Twitter.


text:
Porsche has been carefully monitoring the situation around coronavirus.
We have taken into consideration the latest communication from the World Health Organization and our government's position on the situation and, for now, our Porsche Centre will remain open.
Our number one priority is the safety of our customers, employees and their families. Our team follow strict hygiene protocols and we have reinforced these in line with the latest World Health Organization guidelines. These include hand-washing facilities and hand sanitiser onsite.
We will continue to regularly review the situation and take the recommended precautions to protect our customers and colleagues alike. In the meantime, we would be delighted to welcome you to our Porsche Centre, but recommend that you follow advice from the government and stay at home if you feel unwell.
© 2024 All rights reserved to Porsche Centre Glasgow and its licensors.
*Data determined in accordance with the Worldwide Harmonized Light Vehicles Test Procedure (WLTP) as required by law. You can find more information on WLTP at www.porsche.com/wltp . For Plug-in Hybrid Electric Vehicle (PHEV) range and Equivalent All Electric Range (EAER) figures are determined with the battery fully charged, using a combination of both battery power and fuel.
Values are provided for comparison only. To the extent that fuel and energy consumption or CO₂ values are given as ranges, these do not relate to a single, individual car and do not constitute part of the offer. Optional features and accessories can change relevant vehicle parameters such as weight, rolling resistance and aerodynamics which may result in a change in fuel or energy consumption and CO₂ values. Vehicle loading, topography, weather and traffic conditions, as well as individual driving styles, can all affect the actual fuel consumption, energy consumption, electrical range, and CO₂ emissions of a car.
** Important information about the all-electric Porsche models can be found


text:
Scorned Lover
Scorned Lover | |
Mike about to kill the film extras | |
Game | GTA Advance |
For | Asuka Kasen |
Target | Biff Rock |
Location | Bedford Point, Staunton Island, Liberty City |
Reward | $10,000 |
Unlocks | Sue Me Sushi |
Scorned Lover is a mission in Grand Theft Auto Advance, given to protagonist Mike by Yakuza co-leader Asuka Kasen from a building in Bedford Point on Staunton Island, Liberty City.
Asuka Kasen had attempted to use her 'womanly advances' on film star Biff Rock, who rejected them. Asuka wants him dead and his alligator shoes brought back as a memento. Mike drives to the film set in Bedford Point and sees some of the movies filming process, with Biff Rock playing Jonnie and an actress playing Mary. Biff, however, realises he made a mistake and tells the extras he can not act with so many distractions, such as Mike being on the set. His bodyguards attempt to get Mike off the set, however, Mike kills all the bodyguards, which is filmed by the crew. An impressed Biff tells Mike that he could make him a film star. Mike decides against becoming a film star and gives over the rights to the footage in exchange for his alligator shoes. The police begin to pursue Mike but Mike manages to lose them and returns to Asuka's. Mike hands over the alligator shoes to give Asuka the impression that Biff Rock is dead.
Asuka Kasen: Mike-san, you wouldn't dare spurn my womanly advances, would you? Well that's exactly what Biff Rock, the movie star, did to me! I don't take kindly to rejections. I want him dead!
Mike: Hmm, movie stars normally have bodyguards around them. This is going to cost you and I want to hear some info about my partner and the bartender's deaths soon.
Asuka Kasen: My agents are tracing every lead down, you can be sure. Oh, one more thing. Bring me back his alligator shoes - a memento to remember him by.
Mike: I'll be dead before I let her reminisce about me like that... eh, yeah.
(Mike drives to the film set in Bedford Point)
Mike: Hmm, looks like they're in the middle of shooting a scene.
Mary: Why you doin' this to me, Jonnie? Don't you know I love you?
Jonnie (Biff Rock): Love is tough, Mary. That's why I gotta put you down.
(Biff and his co-stars stop acting)
Biff Rock: Dammit, I forgot to kiss her first! I can't get into my character role with these constant distractions! Please remove this drifter from the set.
(Mike kills the bodyguards)
Biff Rock: Cut! Cut! Fantastic, we got it all on film! Kid, you were amazing! All that violence and blood! And it's real! Hollywood will never know...I tell you what, I'm going to make you a big star, what do you say?
Mike: Never thought much of fame and my reputation's too tarnished for me to become a polititian. I'll make you a deal though, give me those alligator shoes of yours and I'll give you the rights to the footage.
Biff Rock: Done. You'll love this next scene where Liberty City rises up against Mary's killer. That's you, kid. Roll tape... action!
Mike: You've got to admire a guy who's willing to turn Asuka down even if he's a member of the 'Give America Back to Foreign Powers' lobbyist group. Enjoy your freedom away from Asuka, Biff.
Asuka Kasen (pager): Stop acting like a movie star, Mike-san! Get out of there! Lose the police before coming back. Asuka.
(Mike loses the police and returns to Asuka's)
Asuka Kasen: Ahh, K-chan, you amaze me with your success. Let me see the shoes! Ahh, beautiful! Come with me to my trophy case in my bedroom...
Mike: I'd rather not. What interests me is hearing more about leads you have to the assassin's identity.
Asuka Kasen: You disappoint me, K-chan but no matter. The assassin you are looking for is the same that is responsible for your partner Vinnie's death. I'm tracking down his location now. As soon as I know, you'll know.
Post Mission Pager Script
Asuka Kasen: Mike-san, I got a fishy problem. Come soon! Asuka.
The reward for completing the mission is $10,000. The mission Sue Me Sushi is unlocked by completing the mission.
Video walkthrough
GBA Version - GTASeriesVideos |
<youtube>ypRAoKo0thM</youtube> |


text:
I recently had to reinstall the OS on my MacBook Pro. I used MobileMe to sync a bunch of my settings back to my computer (including Keychains), and now I can't see any of my Keychain passwords. If I try to view an item and check the "Show password" or "Show note" checkbox, I get a little alert that says "Access to this item is restricted". However, the Access Control tab for that same item has the "Allow all apps access" option selected, with the description saying "Access to this item is not restricted".
Things I've found/tried:
- Keychain First Aid reports no errors with my keychain.
- There is nothing in my ~/Library/Keychains/.syncinfo folder.
- Creating a new default keychain a re-syncing from MobileMe does not fix the issue.
What do I need to do to fix my keychain? I have a bunch of stuff in there (mostly application license keys) that I'd rather not lose.


text:
Clean Pro Asheville
The best gutter cleaning service and Maintenance Asheville has depended on for years!
You don't have to worry about cleaning your clogged gutters and downspouts any longer! We are the trusted choice for the best professional Asheville gutter cleaning services. Asheville Gutter Cleaning is the preferred choice for gutter and downspout cleaning. Our trained specialists thoroughly examine your downspouts and gutter systems to determine how to most effectively clean your gutters. Our Asheville Gutter Cleaning experts will take care of any clogged gutters. We are your best choice for top-quality gutter cleaning services in Asheville, North Carolina and the surrounding area.
Asheville ( ASH-vil) is a city in, and the county seat of, Buncombe County, North Carolina. Located at the confluence of the French Broad and Swannanoa rivers, it is the largest city in Western North Carolina, and the state's 11th-most populous city. According to the 2020 census, the city's population was 94,589, up from 83,393 in the 2010 census. It is the principal city in the four-county Asheville metropolitan area, which had a population of 424,858 in 2010, and of 469,015 in 2020. == History == === Origins === Before the arrival of the Europeans, the land where Asheville now exists lay within the boundaries of the Cherokee Nation, which had homelands in modern western North and South Carolina, southeastern Tennessee, and northeastern Georgia.
Albemarle, Albemarle Park, Asheville Pocket Neighborhoods, Asheville Township, Asheville metropolitan area, Ballentree, Biltmore Park, Biltmore Village, Burton Street, Chestnut Hills, Deaverview, Downtown, E.W. Grove Park, East End - Valley Street, East View Association


text:
Armelia McQueen, Known for Broadway's Ain't Misbehavin', Dies at 68
Armelia McQueen, who had memorable turns in Broadway's Ain't Misbehavin' and the movie Ghost, died on October 3 at the age of 68. The news was shared by friends on social media on October 4.
Born on January 6, 1952 in Southern Pines, North Carolina, McQueen attended Herbert Berghof's Drama School. She made her Broadway debut in 1978 in the Tony-winning revue Ain't Misbehavin' alongside Charlayne Woodard, Ken Page, Nell Carter and André De Shields, who paid tribute to his former co-star on Twitter. McQueen also appered in the 1988 Broadway revival of Ain't Misbehavin'. She also appeared on Broadway in Harrigan 'n Hart.
Her screen numerous credits include playing Whoopi Goldberg's sister in Ghost as well as the Red Queen in the Disney Channel's 1990s series Adventures in Wonderland and the recurring role of Shula Whitaker in The CW's Hart of Dixie. She also made appearances on screen in Sparkle, Bulworth, Life, Martin, Fresh Prince of Bel-Air, That's So Raven, Brooklyn Nine-Nine and more
Watch McQueen in Ain't Misbehavin''s 1978 Tony performance below!


text:
It's a few years old, but [Brian360's] method of unlocking the hard drive on his Mitsubishi Multi-Communication System is quite interesting. Mitsubishi describes their MMCS as a human-vehicle communication tool. It's basically an in-dash screen and controls to display navigation maps and play music. [Brian] found that the hard drive for the MMCS in his 2008 Lancer was locked, and could not be cloned and swapped out for a larger drive. Sound familiar to anyone? Hard drive locking has been used in many systems, including the original Xbox, which we'll get back to in a minute.
The setup seen above was used to grab the hard drive password from the system itself. A custom adapter card was built and plugged in between the hard drive and the MMCS hardware, with test points for each of the data line. [Brian] attached a digital storage oscilloscope, and after a bit of poking around, found a way to trigger the scope when the password was requested. He explains the process of converting the captured data into an ASCII string password.
With that in hand how would you unlock the drive? The favorite tool for this is hdparm, a tool which was used with early Xbox unlocking but which is still in use with other hardware today. Now brian has a disk image backup and the ability to swap out for larger hardware.
[Thanks Traitorous8]


text:
Myths of Women's Weight Training and Female Bodybuilding
It never fails. It seems like nearly each time we take on a new female client they get so worried to lift more than 3 pounds that they are going to end up looking like a bodybuilder and lose precious flexibility. I am left trying to give the same speech about myths surrounding this subject that I sound like a broken record and I get tuned out fast. Well, below is an article by expert Hugo Rivera who sets the record straight. WOMEN, please read this, it is a great article discussing questions that goes through most of your minds when adopting a strength training routine to help with weight loss and muscle toning.
Women Bodybuilding Myths
By Hugo Rivera
Women's Weight Training Myth #1 -Weight training makes you bulky and masculine.
Due to the fact that women do not, and cannot, naturally produce as much testosterone (one of the main hormones responsible for increasing muscle size) as males do, it is impossible for a woman to gain huge amounts of muscle mass by merely touching some weights. Unfortunately, the image that may come to your mind is that of professional female bodybuilders. Most of these women, unfortunately, use anabolic steroids (synthetic testosterone) along with other drugs in order to achieve that high degree of muscularity. In addition, most also have good genetics coupled with an unbelievable work ethic that enable them to gain muscle quickly when they spend hours in the gym lifting very heavy weights. Believe me when I say that they do not look like that by accident. Women who conduct weight training without the use of steroids get the firm and fit cellulite-free looking body that you see in most fitness/figure shows these days.
Women's Weight Training Myth #2 – Exercise increases your chest size.
Sorry girls. Women's breasts are composed mostly of fatty tissue. Therefore, it is impossible to increase breast size through weight training. As a matter of fact, if you go below 12 percent body fat, your breast size will decrease. Weight training does increase the size of the back, so this misconception probably comes from confusing an increase in back size with an increase in cup size. The only way to increase your breast size is by gaining fat or getting breast implants.
Women's Weight Training Myth #3 – Weight training makes you stiff and musclebound.
If you perform all exercises through their full range of motion, flexibility will increase. Exercises like flyes, stiff-legged deadlifts, dumbbell presses, and chin-ups stretch the muscle in the bottom range of the movement. Therefore, by performing these exercises correctly, your stretching capabilities will increase.
Women's Weight Training Myth #4 – If you stop weight training your muscles turn into fat.
This is like saying that gold can turn into brass. Muscle and fat are two totally different types of tissue. What happens many times is that when people decide to go off their weight training programs they start losing muscle due to inactivity (use it or lose it) and they also usually drop the diet as well. Therefore bad eating habits combined with the fact that their metabolism is lower due to inactivity, and lower degrees of muscle mass, give the impression that the subject's muscle is being turned into fat while in reality what is happening is that muscle is being lost and fat is being accumulated.
Women's Weight Training Myth #5 – Weight training turns fat into muscle.
More alchemy. This is the equivalent of saying that you can turn any metal into gold; don't we wish! The way a body transformation occurs is by gaining muscle through weight training and losing fat through aerobics and diet simultaneously. Again, muscle and fat are very different types of tissue. We cannot turn one into the other.
Women's Weight Training Myth #6 – As long as you exercise you can eat anything that you want.
How I wish this were true also! However, this could not be further from the truth. Our individual metabolism determines how many calories we burn at rest and while we exercise. If we eat more calories than we burn on a consistent basis, our bodies will accumulate these extra calories as fat regardless of the amount of exercise that we do. This myth may have been created by people with such high metabolic rates (hardgainers) that no matter how much they eat or what they eat, they rarely meet or exceed the amount of calories that they burn in one day unless they put their mind to doing so. Therefore, their weight either remains stable or goes down.
Women's Weight Training Myth #7 – Women only need to do cardio and if they decide to lift weights, they should be very light.
First of all, if you only did cardio then muscle and fat would be burned for fuel. One needs to do weights in order to get the muscle building machine going and thus prevent any loss of muscle tissue. Women that only concentrate on cardio will have a very hard time achieving the look that they want. As far as the lifting of very light weights, this is just more nonsense. Muscle responds to resistance and if the resistance is too light, then there will be no reason for the body to change.
Women Should Train Hard
I have trained with girls that train as hard as I do and they look nothing but feminine. If you want to look great, don't be afraid to pick up the weights and lift hard!


text:
Contact Us
Contact our corporate or local offices directly.
An electronics design is a collection of connected components. The rewarding part of product development is coming up with cool ways of solving those engineering challenges, connecting those components to craft your unique design.
However, a large part of the work, and to many designers the more tedious part, is creating the components. While it might not be exciting, the components become a valuable resource for your company, and it's essential that they a
ccurately represent the real-world component.The component that you buy and solder onto the board is the real component, but that component has to be modeled in each of the electronic design domains that you want to use it in.
Depending on what type of design implementations you plan to perform, your component could include: a symbol for the schematic; a simulation model for the circuit simulator; an IBIS model for signal integrity analysis; a pattern or footprint for PCB layout; and a 3D model for visualization, 3D clearance checking and export to the mechanical CAD domain.
Read more about Understanding Models, Components and Libraries.
Each component is a collection of linked models, and parametric component data. It is the models that contain the detailed information needed by each design domain.
The following models types can be used:
Schematic symbol | The symbol represents the component on the schematic sheet. The symbol is created using standard drawing objects, the pins add the electrical properties. | |
SPICE model | Simulate the behavior of the connected components using the SPICE simulator. SPICE models are usually sourced from the device suppliers. | |
Signal Integrity model | PCB interconnects are becoming part of the circuit as device and circuit switching speeds increase. IBIS models describe the pin behavior, allowing Altium NEXUS's signal integrity simulator to analyze the routes. | |
PCB footprint | Each component needs to have a place defined on the PCB where it mounts and connects - the footprint is the model that defines that PCB space. A PCB footprint is created from a set of standard objects, with the pads providing the connectivity. | |
3D model | Today's electronic product is compact and tightly packed, comes in an unusual shape, and may well have a PCB that is folded to fit into the case. To design a product like this you need to be able to model the PCB in 3D - so you can visualize the finished board, perform 3D clearance checking, and transfer the loaded board to the mechanical CAD domain. To do this, you'll need a 3D model of each component. |
The Understanding Models, Components and Libraries page includes links to learn more about creating models.
So how do the models come together to create a component? There are essentially three approaches:
Regardless of the storage option, the model links and parametric data is added to the symbol, creating the design component.
Read more about The Component.
An Altium NEXUS library is an arbitrary collection of models or components. How the models or components are organized into libraries is up to you. You might structure your libraries around device suppliers, or you might cluster components by function, for example with a library for all of the microcontrollers your company uses.
The following library types are available:
Schematic library | At the simplest level is the schematic library (*.SchLib). A SchLib can be a model library, holding component symbols; or if model links and parametric data is added to each symbol, it becomes a component library. |
PCB library | A library for storing PCB footprint models. If required, a 3D model can be added to each footprint. 3D models are created from 3D body objects, or a STEP model imported into a 3D body object. |
Integrated Library | Prefer to have your components pre-packed and pre-verified in a single file? Then compile the source schematic/PCB/simulation models to generate an integrated library (IntLib). |
Database Library | Want to tightly couple the design components to your company data? Then explore database libraries. |
Altium Vault | Want easy, company-wide access and management of your components, with revisioning, where-used and direct coupling to real-time supplier data? Then an Altium Vault could be a good choice. |
Read more about The Libraries.
Contact our corporate or local offices directly.


text:
Costco experiences net, same-store sales jump for September
NEW YORK — Costco Wholesale reported a better-than-expected 6% rise in September same-store sales, helped by higher gasoline prices and a stronger dollar.
Excluding the impact of gasoline prices and foreign exchange, comparable same-store sales rose 5% for the month.
Net sales rose 8% to $9.31 billion in the five weeks ended Sept. 30. Costco, which currently operates 608 warehouses, said it plans to open up to 14 new warehouses prior to the end of calendar year 2012.


text:
Hijacking Google search results for fun, not profit: UK SEO uncovers XML sitemap exploit in Google Search Console
In 2017, Google paid nearly $3 million to individuals and researchers as part of their Vulnerability Reward Program (VRP), which encourages the security research community to find and report vulnerabilities in Google products.
This week, Tom Anthony — who heads Product Research & Development at Distilled, an SEO agency — was awarded a bug bounty of $1,337 for discovering an exploit that enabled one site to hijack the search engine results page (SERP) visibility and traffic of another — quickly getting indexed and easily ranking for the victimized site's competitive keywords.
Detailed in his blog post, Anthony describes how Google's Search Console (GSC) sitemap submission via ping URL essentially allowed him to submit an XML sitemap for a site he does control, as if it were a sitemap for one he does not. He did this by first finding a target site that allowed open redirects; scraping its contents and creating a duplicate of that site (and its URL structures) on a test server. He then submitted an XML sitemap to Google (hosted on the test server) that included URLs for the targeted domain with hreflang directives pointing to those same URLs, now also present on the test domain.
Hijacking the SERPs
Within 48 hours, the test domain started receiving traffic. Within the week, the test site was ranking for competitive terms on page 1 of the SERPs. Also, GSC showed the two sites as related — listing the targeted site as linking to the test site:
This presumed relationship also allowed Anthony to submit other XML sitemaps — within the test site's GSC at this point, not via ping URL — for the targeted site:
Understanding the scope
Open redirects themselves are not a new or novel problem – and Google has been warning webmasters about shoring up their sites against this attack vector since 2009. What is noteworthy here is that utilizing an open redirect worked to not just submit a rogue sitemap, but to effectively rank a brand-new domain, brand-new site, with zero actual inbound links, and no promotion. And then to get that brand-new site and domain over a million search impressions, 10,000 unique visitors and 40,000 page views (via search traffic only) in three weeks.
The "bug" here is both a problem with sitemap submissions (the subsequent sail-through GSC sitemap submissions are alarming) and a greater problem as to how the algorithm immediately applied all the equity from the one site across to the completely separate and unrelated domain.
I reached out to Google with a series of detailed questions about this exploit, including the search quality team's involvement in pursuing and implementing a fix, and whether or not they are able to detect and take action on any bad actors that may have already exploited this vulnerability. A Google spokesperson replied:
When we were alerted to the issue, we worked closely across teams to address it. It was not a previously known issue and we don't believe it had been used.
In response to questions about changes with respect to sitemap submissions, GSC and the transfer of equity affecting results, the spokesperson said:
We continue to recommend that site-owners use sitemaps to let us know about new & updated pages within their website. Additionally, the new Search Console also uses sitemaps as a way of drilling down into specific information within your website in the Index Coverage report. If you're hosting your sitemaps outside of your website, for proper usage it's important that you have both sites verified in the same Search Console account.
I discussed this exploit and the research at length with Anthony.
The research process
When asked about his motivations for pursuing this work, he said, "I believe an effective SEO is someone who experiments and tries to understand things behind the scenes. I've never done any black-hat SEO, and so set myself the challenge of finding something on that side of things; primarily for the learning experience and as a way to run defense if I ever saw it in the wild."
He added, "I like doing security research as a hobby on the side, so decided that rather than take the 'traditional' black-hat route of manipulating the algorithm's ranking signals, I'd see if I could instead find an outright bug in it."
Oftentimes, the driving motivation in pursuing a given method relates to having experienced (or having a client that has experienced) a sudden drop in SERP traffic or rankings. Anthony noted, "At Distilled, like so many SEOs, I've worked with sites that have had unexplained drops. Often clients claim 'negative SEO,' but usually it is something far more mundane. What is worrying about this specific issue is [that] typical negative SEO attacks are detectable. If I spam you with low-quality links, you can find them, you can confirm they exist. With this issue, it appears an attacker could leverage your equity in Google and you would not know."
Over the course of four weeks' evenings and weekends spent delving into it, Anthony discovered that combining different research streams he'd begun proved effective where each separately led to dead ends. "I had ended up with two threads of research — one around open redirects, as they are a crack in how sites work that I felt could be leveraged for SEO — and the other was with XML sitemaps and trying to make Googlebot error out when parsing them (I ran about 20 variations of that, but none worked!). I was so deep into it at this point, and had a revelation when I realized these two streams of research could perhaps be combined."
Reporting and resolution
Once he realized the impact and harm that could be done to sites, Anthony reported the bug to Google's security team (See complete timeline in his post). As this method was previously unknown to Google but clearly exploitable, Anthony noted, "It is a terrifying prospect that this could have already been out there and being exploited. However, the nature of the bug would mean it is essentially undetectable. The 'victim' may not be affected directly if their equity is used to rank in another country, and then the victims become the legitimate companies who are pushed down the rankings by the attacker. They would have no way to tell how the attacker site was ranking so well."
As noted above, the Google spokesperson said they do not believe it has been used. Unclear from their response is whether or not they have data available that would enable them to detect pinged sitemaps used in such a way. If further comment or information is given, we'll update this post.
On the issue of detection specifically, I asked Anthony to speculate on scaling this exploit. "The biggest weakness with my experiment was how closely I mimicked the original site in terms of URL structure and content. I had a bunch of experiments prepped that were designed to measure just how different you could make the attacker site: Do I need the same URL structure as the parent site? How similar must the content be? Can I target other languages in the same country as the victim site? In my case, I think I could have re-run with the same approach but have differentiated the attack site slightly more, and probably [would] have escaped detection," he said.
He added, "If I had kept it to myself, then I imagine I could have gone for months or years. If you outright scammed people it would be short-lived, but if you used the method to drive affiliate traffic, or even simply to boost your own legitimate business, then little reason you'd ever be caught."
As the image below demonstrates, the short-lived traffic driven to the test site was potentially far more valuable than the relatively small (by comparison) bounty he was awarded, which makes one wonder if the security team really understood the implications of the exploit.
Anthony's motivations (and why he did report the vulnerability right away) were rooted in research and helping the search community, however.
"Doing this sort of research is a learning experience, and not about abusing what you find. In the industry, we have our complaints about Google at times, but [to] a consumer, they provide a great service, and I think good SEOs actually help with that — and this is basically an extension of the same idea. The Vulnerability Reward Program they run is a nice incentive to focus research efforts on them rather than elsewhere; it is nice to potentially be awarded a bounty for the time and effort that goes into the research."


text:
I think this is it, friends. I feel so bad, so often, for not
posting enough. So bad that when I do post, all I manage to ramble on about is how busy I
am and how bad I feel, and that, you don't need me to tell you, is a giant
When I started this blog six and a half years ago (!), it
was a new medium. I was new to Paris. I was looking for an efficient way to
stay in touch with family and friends while living thousands of miles away in
the City of Light (and Dark Chocolate). The funny thing about blogs, of course,
is that they're public. Soon enough, strangers were reading my posts. Then
commenting. Then entering my world and becoming my friends.
This blog has been an amazing experience. When I was living
in Paris, it helped me capture, process and translate my life: all the exhilarating
experiences and profound moments and situations of lost-in-translation
confusion. It helped me better understand my thoughts, ideas and feelings. It led to my
Even when I returned to New York, it kept me connected to
Paris—to the community I knew and the friends I had made there. But now I'm cranking
away as a creative director in New York. I'm in the thick of
Parker's toddlerhood, and her endearing growth and discoveries. If and when I
have downtime, all I really want to do is thumb through Vanity Fair or lounge
on the couch with Andrew or play with Parker. Or nap.
So it's time to call it quits. I love this blog and all
it's been and meant to me. I love all you who still follow me and have shared
the journey. I have nothing but gratitude and happy feelings. But I don't want
to be a bore. And I don't want to feel bad. So I'm doneski.
That said (!), I'm hoping there will be a sequel to the book. In which
case, I will need a "platform." In which case, I might hit restart. In which
case, I will let you know. I hope you'd consider joining me again somewhere down
the road. In the meantime, let's stay in touch on Facebook, Instagram and/or
email (firstname.lastname@example.com).
Gros bisous.
Amy xo


text:
Friday, November 18, 2011
{the little things} :: my week in pictures
12 comments:
- The Olive Tree Blog said...
I am not really sure if I even read you post b/c I was still dreaming about your coffee...lol...monopoly...not my thing...however my husbands LOVES it we own 5 different monopoly games...lol :)
- November 18, 2011 at 9:45 AM
- Jana said...
I've tried getting my husband to play monopoly with me like 6 times in the past two weeks. I have yet to convince him, but I'll keep trying! :)
- November 18, 2011 at 12:36 PM
- Nicole @ Sew Much Sunshine said...
Yum yum yum. I love summing up a week in pictures! :)
- November 18, 2011 at 1:57 PM
- TheUnSoccerMom said...
ice cube tray?? GENIUS!!!
I'm so in need of some pumpkin spice ANYTHING!
great post! :o) - November 18, 2011 at 3:44 PM
- Lindsey said...
looks like a good week! and what a great idea with the ice cube tray!
- November 18, 2011 at 6:42 PM
- Lindsay Maree said...
Oh, how I love the pumpkin spice latte from Starbucks. :)
And seriously, using an ice cube tray for your hair clips is the best idea ever! Thanks for the tip! - November 18, 2011 at 10:47 PM
Oh man... Monopoly? I am the WORST at that game! We definitely need to start game nights in our house with other games though! How fun!
I definitely requested to follow you on Instagram! Love you pictures and it's my new obsession!! - November 18, 2011 at 11:33 PM
- Laura Beth said...
hey friend! sorry i'm stopping by so late! we both had the pumpkin spice muffin bug! :) I too think your icecube tray is a great idea. I could use several of those for lillypie things. happy weekend!
- November 19, 2011 at 2:35 PM
- Becca at One Girl said...
What a great organizer for cute bobby pins. I always lose mine.
- November 20, 2011 at 6:38 PM
- Becca at One Girl said...
What a great organizer for cute bobby pins. I always lose mine.
- November 20, 2011 at 6:38 PM
- Unknown said...
LOVE monopoly! and great job on the thank yous! I don't think I ever did get mine all done :(. oh well! Gorgeous scarf, too!
- November 21, 2011 at 12:09 AM
- Holly said...
I love the flower hairclips! :)
- November 21, 2011 at 3:28 AM


text:
Mr Smith opened proceedings explaining he takes decisions on behalf of Vince Cable on licensing the export of military and 'dual use' goods. This involves a two stage process:
- The first question is does it need a licence? The yes or no depends in most cases on whether it is on a control list. The control list is governed by the Wassenar arrangement agreed by 41 key countries involved in arms exports. The content of the list depends on which civilian goods have military application. So for example if something contained cryptography it could be refused a licence. If it is decided that the goods/services do need a licence then
- They look at "consolidated criteria" against which all export licences issued are judged on a case-by-case basis.
- Got EU legislation in place to block supplies of this kind of tech to Syria. Mr Smith's team worked as technical secretariat to the EU on this.
- The UK took the lead to put this on the table at Wassenar. The technology at the heart of the controversy was not controlled and they wanted it to be. The have been two discussions at Wassenar. For an international arms control issue it is moving like lightning - these things can take years - but it still appears to be incredibly slow in practice. He wants it sped up but some countries are procrastinating. The UK are working with the US and Germany to get an international control list. His ministers are behind this but will not back emergency unilateral legislation in the UK
- ECO and BIS are reaching out with various degrees of success to the companies involved in this field.
Eric King from Privacy International was next up. Part of the process he used to research the issue was to attend trade shows for the companies involved in flogging these technologies. He discovered a web of very complicated trading dominated by US, UK and German companies. They get together at trade shows (on surveillance and arms sales). Their product pitches are incredible to listen to. The rule of law, privacy, civil rights don't exist as far as these people are concerned. They act like cowboys. The way they dress - eg black shirts, red jackets & ties - company names like Panopticon, excitable conscience-free talk about facilitating mass surveillance and countrywide interception is the order of the day.
These people are not shipping boxes off the shelf with no idea of what they are doing or who they are dealing with. They are surveillance consultants. They do the installation and the tech support. A UK/German company (who I think he called Gamma?) regulate via DRM the number of intelligence agents who can use the technology; and charge by the number of people they spy on. These companies talk openly at the trade shows and in their promotional materials about spying on political opponents and left leaning universities.
It is really important that export controls be put in place. This is the only way to deal with them. There is a phenomenal amount to be done to hold these companies to account for the terrifying human rights abuses they are perpetrating and facilitating.
Ian Brown then had the opportunity to talk about the GNI digital freedoms report. He opened by asking rhetorically is regulation necessary and then immediately answering yes. If we need it then how do we make it effective?
Some issues that the stakeholders they engaged with raised -
- Dual use - some technologies have military and civilian applications. We cannot ban everything that can be put to nefarious uses
- When is a device a mass surveillance device as opposed to a lawful interception device?
- What about the context e.g use of the technology in countries without the rule of law?
- There is very broad availability of these technologies. So there would be little or no point in taking unilateral action in the UK on them.
- There is a thriving second hand market in these surveillance technologies
- Wassenar had some very sensible rules e.g. there is no point in adding certain goods to the control list because you cannot control their export
- The EU relies on member states to enforce export controls and yet many member states do not have export controls
- Civil society made the point that definitions have to be precise. Too narrow and you miss important stuff. Too broad and you hinder democracy activists who can use technology for positive ends
By and large cryptography control is obsolete. Besides we want democracy activists in repressive regimes to have access to cryptography and easy to use cryptography at that. In one Iranian case Nokia-Siemens equipment was used to find and arrest a 'dissident' activist.
The Communications Assistance for Law Enforcement Act (CALEA) in the US required back doors to be built into communications technologies to facilitate government surveillance.
Nokia-Siemens said they were not going to make any more money out of regimes like Iran. They separated off that branch of the company. Amasys (?), a French company doing business with Libya did the same thing. They sold of that part of the company.
The responsible thing for these organisations to do would be to be transparent about what they have shipped to whom and where.
It is not the only solution to the problem - this has to be tackled on multiple fronts - but export controls can help. There is kit which should be controlled but is not, yet.
Syria and Iran are easy to demonise - they are pariah states. But there is a spectrum. There are numerous other countries the UK patronises that are involved in well documented human rights abuses.
There followed a series of questions from the floor.
To what extent will enforcement be pursued against companies who break the rules?
Mr Smith from ECO replied it is largely a question for the CPS on whether to prosecute. BIS pursue a number of prosecutions every year. They win some and lose some. One of the questions the CPS ask is whether there is a legitimate defence where the company can reasonably plead ignorance of the uses to which their good would be put.
Ian Brown also responded to this question making the point that despite concerns about the effectiveness of export controls, without them all other methods of control will be circumvented. And if we relied on the reputation of companies we would not do business with arms dealers.
The next question related to the extent to which government acts as salesmen for the arms industry - to what extent is the government selling surveillance equipment. Also, hacking tools are not just used for domestic surveillance but for international spying. To what extent are concerns about spying taken into account i.e arming other countries to spy on the UK? What are the concerns about selling zero day exploits abroad?
BIS do not think the UK government are with knowledge aforethought selling surveillance equipment abroad. Do they explicitly take into account whether goods considered for licencing will be used against the UK - yes.
Would it be good if there was an international forum for the control of technology used to abuse human rights? Yes.
Are the UK government going to say they have to protect surveillance technology export in the interests of protecting the export of other technology? No.
The companies that are doing the most damage are software companies that come out of telcos. There are a clutch of these companies around Berlin run by ex- Stasi officers.
Some of these companies have decent motives and genuinely want to supply protective technology and tools to democracy activists. But there are a lot of people in the field who are glorying in dealing with despotic regimes, wreaking havoc and having a whale of a time, says Eric King of PI.
There was a question about the Communications Data Bill (CDB aka the Snoopers' Charter). Mr Smith from ECO BIS is confident that the motivation of those pushing the CDB is pure.
Specialist companies dealing in this area do not respond well to external pressure. We have to put export controls in place and sue them. A couple of recent cases have been pursued against Cisco under the US Alien Torts Act accusing them of aiding and abetting torture and imprisonment. It can be difficult to get evidence but if companies are selling stuff and don't do due diligence they should be held liable.
The final comment from the floor was that pressure should be applied to the venture capitalists funding these companies.
A concluding comment was then requested from the three panelists.
Ian Brown emphasised the point that it is principally governments who can make a difference. Ethical consumerism would help as would ethical capitalism on the part of the companies involved in these technologies.
Tom Smith said it is difficult but important to get these technologies under control and BIS are working hard to that end.
And finally Eric King said it is really important to get export controls on this stuff. That rounds off the notes on the second panel but I think it is worth finishing with the executive summary and recommendations from the report again. Plus a recommendation that it is essential reading for anyone with an interest in digital freedoms in international law.
"With around 2.3 billion users, the Internet has become part of the daily lives of a significant percentage of the global population, including for political debate and activism. While states are responsible for protecting human rights online under international law, companies responsible for Internet infrastructure, products and services can play an important supporting role. Companies also have a legal and corporate social responsibility to support legitimate law enforcement agency actions to reduce online criminal activity such as fraud, child exploitation and terrorism. They sometimes face ethical and moral dilemmas when such actions may facilitate violations of human rights. In this report we suggest practical measures that governments, corporations and other stakeholders can take to protect freedom of expression, privacy, and related rights in globally networked digital technologies. These are built on a detailed analysis of international law, three workshops in London, Washington DC and Delhi, and extensive interviews with government, civil society and corporate actors. "Even if you're not a digital policy geek, the full executive summary (page 4-7) and the recommendations (p41-44) should be essential reading for everyone.


text:
Bitcoin ATM South Gate - Coinhub
Coinhub Bitcoin ATM in South Gate, California
Our Coinhub Bitcoin ATM Near Me in South Gate, California is available for purchasing bitcoin with cash instantly. Coinhub offers $25,000 daily limits and lowest rates for Bitcoin. Automated Teller Machines (Bitcoin ATMs) allow you to buy Bitcoin and other cryptocurrencies using cash. Bitcoin cash kiosks from Coinhub are a convenient and fast way to purchase Bitcoin and receive it in minutes directly into your wallet. Coinhub Bitcoin machines are easy to use and allow buying at our btc atm to be fast and instant. If you're using a Coinhub Bitcoin Machine near me, you are able to purchase Bitcoin instantly and receive it within minutes. You can purchase Bitcoin in less than 2 minutes, and you don't need an account. Simply walk up to any Coinhub Bitcoin ATM to purchase and verify. Many Coinhub Bitcoin ATMs allow you to buy and sell crypto for cash. You can buy Bitcoin using one our Bitcoin ATMs. First, locate the nearest Bitcoin ATM in your area by visiting our Coinhub Bitcoin ATM Locator. Walk up to the machine and enter your phone number. You will then verify your phone with a code and scan your bitcoin wallet. Enter each bill one at a time to determine the amount you wish to purchase. After that, confirm the purchase by entering the bitcoin atm. Bitcoin is then instantly sent to your wallet. The daily limit for buying Bitcoin is $25,000. There are Bitcoin Machines located in major cities across the country. Visit a Coinhub Bitcoin ATM today.
This Coinhub Bitcoin ATM is located inside H & D Liquor at 3233 Tweedy Boulevard, South Gate, CA 90280. It allows you to buy Bitcoin at any of the following locations and near neighborhoods: Watts, Florence-Graham, Walnut Park, Willowbrook; Southeast Los Angeles, Harbor Gateway North; East Rancho Dominguez, West Rancho Domingues, South Central; Athens, South Los Angeles, Vernon/Main, East Los Angeles, Boyle Heights, Rancho Dominguez, Vermont Harbor; El Rancho Dominguez, Vermont Harbor; El Rancho Dominguez, Vermont Harbor; El Rancho Dominguez, El Rancho Dominguez, Vermont Harbor; El Rancho Dominguez
27th Street Historic District, Addams, Arlington, Avalon Gardens, Bandini, Belvedere, Belvedere Gardens, Bridgedale, Carson Park, Central Alameda, Cherry Manor, College Square, Coolidge Triangle, Downey Landing, Downtown Compton


text:
We live in a world where the population is rapidly increasing. The most astounding aspect of it is that no actions are being taken to reduce the rate of unemployment. There are few options accessible for the many people who are qualified in one or more fields. People's sole option is to choose a auditing company that they believe will provide them with excellent service. This is not a guarantee because there are numerous companies with which they are unsure which is the finest to work with. When it comes to selecting the ideal organization, there are a number of aspects to consider. It is however not mandatory that because you have the factors to look into that you will definitely be able to secure the best auditing company. A lot of sacrifices are necessary in order to be able to achieve your intended target.
As it was pointed earlier on, when you want to choose the best auditing company, it is necessary that you take into account the most apt factors that will enable you to secure what you want. Location is one of the most appropriate factors to look into when you want to choose the best auditing company. It is good to get rid of the notion that with resources made available and in this case capital, you will settle down with the auditing company of your choice not minding where it is located. Location forms part and parcel of those technical factors that if you take them for granted, you will have yourself to blame should you get a problem related to it. The issue of location comes out well when it is strategic at that. It is prudent that you choose the reliable Tax cpa Greensboro NC company which you are sure is near your place of residence for the purpose of accessing it.
The second factor that you need to look into when choosing the best auditing company is expertise. It is good to first of all ask yourself the influence the aspect of expertise has towards the choice of the best auditing company. The essence of choosing the this company which is the best at that is to be offered the best services. The best services will be offered by people who are qualified and experts at that. On that note, it is good to choose the auditing company which you are sure it hires experts to administer quality services to its clients.
Lastly, when you want to choose the best auditing company, it is paramount that you take into account the idea of cost. It is good to always make sure you know what you have and what you intend to achieve. Looking into the idea of cost, you first need to identify the services that you want to have from that auditing company in question. It is good to choose the auditing company with which you are sure that it offers quality services which are proportional to the cost you are likely to incur. Choose the auditing company which is friendly to your pocket.


text:
Space Advocacy: A Guide to Getting Involved
"Space is big. Space is really big. It is so big you probably cannot comprehend just how big it is..."
If you recognized that quote from "The Hitch Hikers' Guide to the Galaxy" then congratulations! You are a good candidate for Space activism. If you didn't get the reference, never mind you are still a good candidate! A lot of people are aware of Space and some of the value it brings to our lives, but Space like the environment, needs good promoters so the rest of the world knows what Space is really about.
Anyone can be a good Space activist. It is also easy to do. It takes a little bit of time, occasionally costs a little money but most of all is the desire to make a difference. If you fit these criteria, then you are ready to start down a fun and exciting path.
Probably the first step is to find an organization that suits your personal goals and ambitions for Space travel. There are plenty of them each with different objectives. The National Space Society, for example, is politically active not just in the USA but also in numerous countries lobbying for "Space friendly" laws. The Artemis Society is focused on travel to the moon. The Mars Society, as its name implies, is focused on manned exploration of the red planet. Other groups include the Planetary Society, the Space Frontier Foundation, the Space Foundation, etc. All of these are great organizations only each group's core focus is different. Before joining any of them take some time and gather as much information about them as you can. Then pick one or two to join. Usually the annual dues are very reasonable, and you'll get first hand information on what the group is doing to further Space activities. You'll find some great information and there is a lot of fun to be had and many great, interesting and smart people to meet.
Next, you'll want to get involved locally. Most of the national organizations have local chapters (clubs) that hold monthly meetings, assist with educational activities and present information to the general public and politicians alike. The biggest danger with joining a local club however is burnout. The desire to get involved in something new can lead to joining too many projects quickly and becoming overwhelmed. Take your time, be patient and assist with one or two club projects. The amount of glamour work in any group is just a small percentage of the project. There are lots of "nuts and bolts" activities that need to be done. Start with some of these (matching them to your hobbies and interests of course) and you'll be on your way. As for costs, most of the local chapters have annual dues on top of the parent organization's, but they are usually very modest.
Third, get out and talk about Space. This is more than just talking about the Space shuttle around the water cooler. You need to talk about how Space affects people's lives, what it has done for the economy, where it is going, etc. Are you working on a neat idea for something Space related? Share your ideas at meetings like the International Space Development Conference (ISDC). It is a great way to get together with like minded Space buffs. If you like public speaking, you can give a presentation on Space flight at a local business gathering. Maybe you can assist school kids with building rockets. Nothing is better than the look in a child's eyes when they learn something new. It is a great reward to a fun activity.
Finally, show your support for companies in the Space business. They started into the business for a reason - to turn the dream of Space flight for everyone into a reality. It takes a lot of hard work and knowing that people are interested helps these firms continue onward even when times seem bad. The best ways to show your support include sending an email or two or better yet, purchase some of the products they sell (they are in business after all). As a Space entrepreneur, it is nice to know that people out there believe in what you are doing. Showing your support keeps them going.
These few points are just the start. There are as many ideas about what to do in Space as there are stars in the sky. Space is big, it has room for a lot of ideas. But Space needs your support. It starts with you. You are the reason these groups and companies exist. They want to help you turn your Space dreams into something more. Become an advocate and let's go exploring - together.
Joe Latrell is founder of Beyond-Earth Enterprises - a consumer space development company based in Colorado Springs.
Join our Space Forums to keep talking space on the latest missions, night sky and more! And if you have a news tip, correction or comment, let us know at: email@example.com.
Get the Space.com Newsletter
Breaking space news, the latest updates on rocket launches, skywatching events and more!